Tryton Community supports the work on tryton.org to extend the capabilities of the Tryton ERP system. Tryton Community is warm and welcoming, open to all contributions to Tryton.
The policy for Tryton Community, is much more relaxed the tryton.org’s policy.If you follow a few basic rules, it is a gathering place for contributions that have no place on tryton.org, especially
documentation and videos,
tools, for example for installation, administration and documentation,
extensions for core modules providing additional capabilities.
Tryton Community aims to make collaboration on Tryton modules and tools attractive, especially to avoid duplication and multiple efforts. The Tryton Community is intended to be a place where a vibrant and agile Tryton community can grow.
trytoncommunity-setuptool — get rid of all the boilerplate and its
maintainence burden of setup.py
tryoncommunity-cookiecutter-module — an enhanced cookecutter template,
prepared for Tryton Community, using trytoncommunity-setuptool, of
course. (comming soon)
centrally maintained CI/CD pipeline configurations, which can be included in
your project by just adding three lines
A Space for Free Development
Tryton Community creates a space where Tryton development can unfold more freely. Tryton Community wants to make Tryton more accessible especially to users without programming skills. Therefore, we invite all those active in the Tryton project to contribute to Tryton Community.
I’m quite a lot convinced that fellow friend’s @htgoebel approach can be a valuable impulse to widen the angular field, in order to achieve the improvements Tryton deserves. I’m willing to contribute user feedback and a little money as well in that respect.
I just read all the website text and did not find any reference or insinuation of such fact.
If you really have such feeling I may understand it but it do not think its related to this project.
If you want to talk about it count me in. I’m open to a public discussion here on the forum or by any other method you prefer, even privately. You have all my contact details, just reach me if you want to do so.
You hit one of the points which are not finally settled. For us it was more important to start than to have all open questions answered. We prefer to discuss with more people anyway. So please share your ideas here in the forum. (There is no use in splitting the community by implementing another discussion area.)
I have been following the Tryton project for many years (as well as a number of other open source “business software” projects). Imho, when the term “Community” is used with a specific project (e.g. “Moodle Community”, “Nextcloud Community”, “Mantis Community”, “SeedDMS Community”, “Tryton Community”, etc.), it commonly refers to the community most intimately associated with the project, endorsed by the project leadership and supported by the project with infrastructure (such as a public code repository and forum, wiki, mailing list, etc.).
At least initially, tryton.community was intentionally distinct from the “Tryton project” community by it’s own description (although it appears the description on tryton.community has been recently changed, and as web.archive.org has not archived previous revisions I am unable to reference the original text). Consequently, while tryton.community may represent “a” Tryton community, it cannot be held to represent “the” Tryton Community as would be understood by most readers.
This is a cop-out. There is no such thing as “just a name”, names insinuate definitions and determine interpretations.
Imho, both of these names would imply endorsemet by the Tryton project, and in the current discussion would be equally unsuitable. I think the onus should be on the leaders of tryton.community to propose a name to the Tryton Foundation for consideration, and the foundation decide suitability according to the constitution of the foundation and the rules for licensing the Tryton trademark (logo).
Imho, the best outcome is for the Tryton Foundation to understand and accept the validity of tryton.community’s source of motivation and find a way to work together, so that tryton.community can operate with the endorsement of the foundation (and licensing of the logo), and contribute in a coordinated way to the overall success of the Tryton project without fracturing the community.
Before making the project publicity available it has been discussed with the foundation. Indeed the initial proposal was that the foundation hosted a “Tryton Contrib” project to include more code than the current one. This was rejected by the foundation board so the project continued to evolve without the support of the tryton foundation.
First I think that such a place can help small developers and freelances with their source code management. Having everything already laid out and test infrastructure available can also make it more visible.
Second, personally I think that many (if not all) service providers and the bigger developers already have their infrastructure set up and are not going to move to something else. Maybe they would if the place was set up and supported by the Tryton Foundation. But even then, some use Git others use SVN or Mercurial and moving between then will change the (internal) workflow which can be a real pain.
Third, as @dalers pointed out, the name is wrong. I would call it something like tryton.sandbox just to show people that the site is a sandbox where you can play and do things without interrupting the rest of the Tryton Community. The Tryton developers can look over the shoulder and maybe ask for a module to be included in the core.
Fourth, the site seems to be focusing on the German part of the community. Maybe I’m wrong, but then enforce the English language to be used for everything including code, documentation and (code)comments.
We exchanged some emails during the beginning of the summer, @htgoebel proposed what are now the Tryton community rules (or almost those I didn’t read the current ones attentively) and I made some remarks. But they were not even read because he wanted an official statement from the board on his proposal. I hardly call that a discussion.
Anyway a vote was held by the foundation (with a discussion this time). And indeed the proposal did not gather the support of the foundation by a very tight 4 - 3 vote.
Regarding the initiative in itself, it’s a surprise to nobody that I support this kind of project.
At first I didn’t have an issue with the name but for now it seems that it has spurred some misunderstandings, so yeah it would be better if it used another one (I’m not sure it’s technically doable though).
Anyway, we’ll see if it sticks and become a place where people contribute their code and modules or not. I hope people will do it.
Well, to be clear, the request was the approbation, support and creation of this project as-is by the Foundation and then the Foundation must transfer the ownership to 3 individuals but keep supporting the costs.
It seems you are trying to say something with some sentence but it is not clearly said. Following your last remarks it seems you are insinuation something about the project. If so please make it loud as we are here to discuss anything with respect.