-
Notifications
You must be signed in to change notification settings - Fork 381
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We would like to maintain the project in future #165
Comments
Hi @h5gs, I've largely abandoned this project over the last few years because of lack of time. Would you be interested in becoming the main maintainer? It may be better to fork the project to your own account. Then I can update the README.md to point to your active fork. Cheers, |
I will be happy to become main maintainer, I have already pushed my current changes to this repository.. https://github.com/h5gs/NativePosEngine Please point your README.md to above repository. Would love to get access to website too, if possible so that I can keep it alive on same name etc. my skype id is ravindra1237 incase you need to share some other info. |
I would like to help maintain this as well. I really like it. |
hi @h5gs and @jbittner79 and @micwallace i wish to collaborate in mantain with you guys this.. are you still interested in ? please let me know cos i will not work in a dead end place! i checknig the other repo and we can update all the things here? |
Im still down
Joshua S. Bittner
717-440-7275
…________________________________
From: Герхард PICCORO Lenz McKAY ***@***.***>
Sent: Wednesday, August 4, 2021 1:36:32 PM
To: micwallace/wallacepos ***@***.***>
Cc: jbittner79 ***@***.***>; Mention ***@***.***>
Subject: Re: [micwallace/wallacepos] We would like to maintain the project in future (#165)
hi @h5gs<https://github.com/h5gs> and @jbittner79<https://github.com/jbittner79> and @micwallace<https://github.com/micwallace> i wish to collaborate in mantain with you guys this.. are you still interested in ? please let me know cos i will not work in a dead end place! i checknig the other repo and we can update all the things here?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#165 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHKJEVNZWPRJAIK3PY5QFS3T3F3CBANCNFSM4JHLM47Q>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>.
|
ok @jbittner79 so @h5gs ? any hint? @micwallace are you alive? or @jbittner79 doyou plan to return in future? |
Lenz it sounds like we should set some time to discuss where its at and where we want to go. Im in Eastern US time zone. How about you?
Joshua S. Bittner
717-440-7275
…________________________________
From: Герхард PICCORO Lenz McKAY ***@***.***>
Sent: Thursday, August 5, 2021 12:20:12 PM
To: micwallace/wallacepos ***@***.***>
Cc: jbittner79 ***@***.***>; Mention ***@***.***>
Subject: Re: [micwallace/wallacepos] We would like to maintain the project in future (#165)
ok @jbittner79<https://github.com/jbittner79> so @h5gs<https://github.com/h5gs> ? any hint? @micwallace<https://github.com/micwallace> are you alive? or @jbittner79<https://github.com/jbittner79> doyou plan to return in future?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#165 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHKJEVNZVT5SID6RKQME36TT3K23ZANCNFSM4JHLM47Q>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>.
|
i would like to contribute too @rmak78
…On Fri, Aug 6, 2021 at 5:41 AM jbittner79 ***@***.***> wrote:
Lenz it sounds like we should set some time to discuss where its at and
where we want to go. Im in Eastern US time zone. How about you?
Joshua S. Bittner
717-440-7275
________________________________
From: Герхард PICCORO Lenz McKAY ***@***.***>
Sent: Thursday, August 5, 2021 12:20:12 PM
To: micwallace/wallacepos ***@***.***>
Cc: jbittner79 ***@***.***>; Mention ***@***.***>
Subject: Re: [micwallace/wallacepos] We would like to maintain the project
in future (#165)
ok @jbittner79<https://github.com/jbittner79> so @h5gs<
https://github.com/h5gs> ? any hint? @micwallace<
https://github.com/micwallace> are you alive? or @jbittner79<
https://github.com/jbittner79> doyou plan to return in future?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<
#165 (comment)>,
or unsubscribe<
https://github.com/notifications/unsubscribe-auth/AHKJEVNZVT5SID6RKQME36TT3K23ZANCNFSM4JHLM47Q
>.
Triage notifications on the go with GitHub Mobile for iOS<
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android<
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
>.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#165 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAQ4RQWMVU5LPYYSTEKQSPLT3MVVJANCNFSM4JHLM47Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>
.
|
well we are two now.. @rmak78 and @jbittner79 i think the weekend could be the best time to discuss (i proposed the IRC way, i am also in matrix and telegram but i not used so much matrix due are too heavy, see notes), in the meantime we can see if someone else answers, i hope @andriux1990 join us too he improved another pos system .. of course, i guess maybe we will need more skilled people of course, but those will be arrived with the time, and we could learn from them, also let me be clear, although I have collaborated with other projects, I am not proposing myself as a leader, neither forced to anything here! NOTES: IRC is my choice, cos is more light, simple and runs in any device due lightweight protocol, due i am not 100% connected and IRC does not stored older messages in history when disconnected, any messages you guys put me in the #open_debian_devuan irc channel will be redirected to the matrix #open_debian_devuan one and also in telegram open_debian_devuan group.. so |
@rmak78 @jbittner79 I am interested in maintaining this repository in fact I have worked on bug fixes and improvements with @ andriux1990 and @mckaygerhard |
Sounds like there is 4 of us. I will start doing what I can when I can now that I know others are still interested.
Im not trying to be a leader here either per se. Im leader on enough stuff already. I like the project here. Im no guru but im willing to help.
Ive never used IRC but ill figure it out.
Joshua S. Bittner
717-440-7275
…________________________________
From: adga137 ***@***.***>
Sent: Friday, August 6, 2021 9:26:21 AM
To: micwallace/wallacepos ***@***.***>
Cc: jbittner79 ***@***.***>; Mention ***@***.***>
Subject: Re: [micwallace/wallacepos] We would like to maintain the project in future (#165)
@rmak78<https://github.com/rmak78> @jbittner79<https://github.com/jbittner79> I am interested in maintaining this repository in fact I have worked on bug fixes and improvements with @ andriux1990 and @mckaygerhard<https://github.com/mckaygerhard>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#165 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHKJEVKZUMBUL6RPVFDUZMLT3PPH3ANCNFSM4JHLM47Q>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>.
|
as i said you can use telegram or matrix too. same group put message and as i know @adga137 is also on same groups.. so the message will come to us.. i will waith for @adriux1990 response |
Ive never used matrix or telegram either lol
Which does everyone prefer? Ill use it. I have no preference
Joshua S. Bittner
717-440-7275
…________________________________
From: Герхард PICCORO Lenz McKAY ***@***.***>
Sent: Friday, August 6, 2021 1:15:43 PM
To: micwallace/wallacepos ***@***.***>
Cc: jbittner79 ***@***.***>; Mention ***@***.***>
Subject: Re: [micwallace/wallacepos] We would like to maintain the project in future (#165)
Sounds like there is 4 of us. I will start doing what I can when I can now that I know others are still interested. Im not trying to be a leader here either per se. Im leader on enough stuff already. I like the project here. Im no guru but im willing to help. Ive never used IRC but ill figure it out. Joshua S. Bittner 717-440-7275
as i said you can use telegram or matrix too. same group put message and as i know @adga137<https://github.com/adga137> is also on same groups.. so the message will come to us.. i will waith for @adriux1990 response
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#165 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHKJEVJEB3W46PKM3N544SLT3QKD7ANCNFSM4JHLM47Q>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>.
|
Hi, there. I like to work on this too |
Hey guys,
Yeah I'm alive 😂 but I'm no longer working on this project. I hope you can make use of it for your purposes. It hasn't been updated in about 5 years so could definitely use a refresh. If you're looking at making this more useful in the future I'd suggest adding some common API or interface to add integration with ERP and other systems.
Cheers,
Michael
On 6 August 2021 10:41:55 am AEST, jbittner79 ***@***.***> wrote:
Lenz it sounds like we should set some time to discuss where its at and where we want to go. Im in Eastern US time zone. How about you?
Joshua S. Bittner
717-440-7275
________________________________
From: Герхард PICCORO Lenz McKAY ***@***.***>
Sent: Thursday, August 5, 2021 12:20:12 PM
To: micwallace/wallacepos ***@***.***>
Cc: jbittner79 ***@***.***>; Mention ***@***.***>
Subject: Re: [micwallace/wallacepos] We would like to maintain the project in future (#165)
ok @jbittner79<https://github.com/jbittner79> so @h5gs<https://github.com/h5gs> ? any hint? @micwallace<https://github.com/micwallace> are you alive? or @jbittner79<https://github.com/jbittner79> doyou plan to return in future?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#165 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHKJEVNZVT5SID6RKQME36TT3K23ZANCNFSM4JHLM47Q>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>.
-- >
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#165 (comment)
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
that for your response @micwallace we need maybe start a collaboration process and voting.. the only thing we need from you is info in started steps.. so later we can go alone withyout disturbing too much to you.. |
Yeah I'm happy to provide some guidance where I can. I would suggest forking the repo and doing a rename of the project, as I'd rather keep the current one as a historic reference. I'll then update the readme with a link to the official successor project. WallacePOS was always a placeholder name and stuck because I was younger and had a bigger ego :-D
On 9 August 2021 7:25:32 am AEST, "Герхард PICCORO Lenz McKAY" ***@***.***> wrote:
> Hey guys, Yeah I'm alive but I'm no longer working on this project. I hope you can make use of it for your purposes. It hasn't been updated in about 5 years so could definitely use a refresh. If you're looking at making this more useful in the future I'd suggest adding some common API or interface to add integration with ERP and other systems. Cheers, Michael
that for your response @micwallace we need maybe start a collaboration process and voting.. the only thing we need from you is info in started steps.. so later we can go alone withyout disturbing too much to you..
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#165 (comment)
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
Hello Guys, We are soon going to work on this project and going to have dedicated resource from our end. Thanks |
hey @h5gs please advertise us when happened i am ready to collaborate |
A tentative expression of interest my sides. We have a Tyro card reader and need a POS. FreePOS is gone (no long offered). ospos looks fine:https://github.com/opensourcepos/opensourcepos but lacks Tyro support. Looks like I'll be starting by a look at h5gs fork as the likely official WallacePOS repo. As to contribs, I am seriously time poor, but happy to invest a little to getting something running for the clubs I support. We shall see. To be honest, one of my major ineterests in contributing to such FOSS products is to see postgresql supported and anything I need for lighttpd support. As that's the stack I use. |
@h5gs, have cloned your repo locally. But taken a look, and it looks to me that it would benefit from an improved README, on how to install and run in a dev environment (for contributors) and a production environment (for users). I'd see that as a first step I'd be grateful for if you hope to see contributions from others like myself and @mckaygerhard, @nerv55 and @jbittner79. I'll park it for now till I hear back. But am keen to see a demo install locally some time in a dev context and production context. |
@bernd-wechner we are going to start working on this from Monday and we will keep everyone informed here. I will update my repo with latest readme file etc and slowly document it. Just to keep myself emotionally connected and keep moving have rebranded it as NativePosEngine.( Wanted to keep original name but @micwallace current owner is also attached it's original name :) and don't want to loose. Anyway here is the new repo url and will keep updating everyone. |
Cool. Renaming it is fine. I'd keep POS capitlised though if I were you. Why "Native"? Part of me likes FOSSPOS or FOSS-POS ;-). But entirely your call if you're managing the main repo from hereon in. After a slightly deeper look my priorities would be: Update the README with clear installs for dev and production users, and update to use latest PHP and Node.js versions. |
That's nice name suggestion, The more names idea I see and it becomes more confusing to decide the name :) Yes idea was build native app for android/ios and enhance it, will update you soon. |
i develop in ospos and is not good solution.. i needs so many fixeds i made and developer just said "i not in my interest" by example lack of lighttpd good support @bernd-wechner
i like too to mantain the name .. @h5gs
we are in same problem.. my hope is to convince to @nerv55 to be more involved so usage will be the key of development
you just renamed but broke the fork line! can you re-back the fork and made the new repo a fork of? to mantain the link with wallacePOS .. and what about @micwallace ? take in consideration that people that develop at POS system is cos use it.. hat happened when you guys will not used anymore a feature? will be the same behaviour of ospos.. (those guys always said that only work in their own features.. and arges that each people must pull a request with code) -- many good people that have no good coding skills are able to code in complicated scenarios.. i try to make a exampel with @andriux1990 that have a goos folrk and huge improved ospos version with fical printer support (latin america) and credit debt .. so used and not present in most FOSS POS systems |
Thanks for your input and feedback , I have relinked it to main repo. |
@h5gs now enable the issue in the new repo.. please.. thatnks a lot! |
We are software company from Bangalore , India and we have developed few features in this project and happy to send pull request.
Features developed.
Have plans to add more features
We are planning to enhance and work on this with dedicated resources,
Happy to help in maintenance of this project.
The text was updated successfully, but these errors were encountered: