search

h5gs / NativePOSEngine

WallacePOS uses the power of the modern web to provide an easy to use & extensible POS system.
GNU Lesser General Public License v3.0
9 stars 6 forks source link

[task] define mains tasks and guidelines based on old original ones.. #2

Open mckaygerhard opened 3 years ago

mckaygerhard commented 3 years ago

more user behaviour and focus the contribution in funtionality and collaboration event code complexity

Context

Keep in mind that people who develop in the POS system is because they use it ... What happened when you no longer used a function externally developed? it will be the same behavior as opensourcepos .. (those guys always mention that they only work on their own features .. and argue that each person should make a request with code) - many good people who do not have good coding skills are unable to code in complicated scenarios ... but you have a great idea and minimal code skill to do it in an ugly way. we have to take these users into account

justification

  1. first base example was the adempiere vs iDempiere history.. adempiere focused on functionality and iDempiere on code cleanup, adempiere is featured way and idempiere is stable cleanly..
  2. lets searching and looking at opensourcepos problems .. lots of end users and lack of coding users .. At least half of them have good code and contributions but without standards coupled to the project code, if they were to join and others were in charge of adjusting the code, there would be a more powerful application (although with the conscious danger of acquiring bugs or losing stability )

considerations

  1. we need a group member to handle issues and reach out to users who don't have technical skills, so that we can engage more users in contributions (of course later we can force them to learn how to do things more technically), and this member does not need to be an expert in programming .. only minimal knowledge of the code and deployment in the infrastructure in the os.
  2. We need developers to commit to taking care of the code, even the parts that they are not directly responsible, since it is software that handles money, and although the features can be important, stability is the main directive to take care of, because the data can be damaged .

limitations

of course this sound impossible if the code base is so big, and we started with lack of manpowers, but is important, if we plan to make good support and stable CRM, this issue will be a simbolic one

mckaygerhard commented 3 years ago

I have reviewed the number #1 and I see that github now supports discussions (each discussion is a hidden issue), you can enable the discussions as the least technical support, and it is passed to issue when it is determined if it needs code modification or alteration of the operation

h5gs commented 3 years ago

We are soon going to dedicate our time into development/testing etc and it's good that we have you who is taking initiative.

bernd-wechner commented 2 years ago

It's a year later and I don't see much change, so not so soon I guess ;-). Fret not, I am not criticising, it's FOSS, I know the deal. But still, it would be nice to know if you have plans or not?

ravindragit commented 1 year ago

Are you guys still interested to continue this.? We will be working on this project soon.

Sorry we were busy on something related to other stuff.

mckaygerhard commented 1 year ago

i are interested @ravindragit what happened?

bernd-wechner commented 1 year ago

We're super keen. I just want a POS that installs easily on a tablet or laptop or even phone and works with a Tyro. It would make my life in treasury so much easier.

mckaygerhard commented 1 year ago

@bernd-wechner tablet and phones are not a platform of "installation" all the "apps" in your phone are a view of a web page, very little of them are really true application native

most of the phone/tablets apps need newtworking so you almost always will need a server where to deploy your POS system, only a simple and little (poor) POS system can be deployed in the phone/tablet

h5gs commented 1 year ago

Happy to see your responses and willing to keep me available for this.

Hopefully, we can see some progress now.

bernd-wechner commented 1 year ago

@bernd-wechner tablet and phones are not a platform of "installation" all the "apps" in your phone are a view of a web page, very little of them are really true application native

most of the phone/tablets apps need newtworking so you almost always will need a server where to deploy your POS system, only a simple and little (poor) POS system can be deployed in the phone/tablet

That's fine. A mere detail to my mind. As long as it's available on a tablet or phone (I can always host a server for it to talk to) then, native or simply a phone view of the web page is all fine (the notion of app still has value as most people know how to install and find an app, but getting them to use their web browser on a phone is harder)