Add new category for message board

These are the right words! Sometimes I walk into a configuration issue and want to talk about it in the form of a tutorial / howto so others don’t need to search for the solution themselves. I can do it in a blog post etc but it’s way better to have it in the place where it belongs, here.

Why not something like “From the community”? It makes it very clear that everything in that category comes from the community. When things evolve, labels, tags or sub categories can be added.

I guess you mean a subcategory in “News”.
Why not but we have a trouble now because of Announcing tryton.community

Also I think this can be larger and more information than just news.
So for me it is the equivalent of a white board at the office where people write messages and thoughts that are replaced by new ones the next week.

And who knows maybe from those posts the documentation can be made better by including some remarks or clarifying some wording.

Let’s work with example. What kind of topic could be problematic in your point of view?

The proposal is:

But it is not explained when it is place of “message board” (I do not mind about the name) and when it is place of the current organization category.

I’m just asking to clarify which are the criteria used for such new category and others for the new one.
There is an example about “official anouncement” and I asked what is official anouncement.

How can I answer to what topic should be problematic if we never said which kind of topics are expected to be posted on each category? :thinking: :thinking:

Because apparently I understand what the proposed new category is about, @ced understands it and @edbo too.

And as I really don’t understand what you don’t understand then I’d like to work based on example (also because I think it’s not something that can be decided by algorithm but rather by an IA like ChatGPT).

So please provide me some example of topics and I’ll let you know in which category I would put them.

I’ll start with some recent examples:

  • “Announcing tryton.community” → Message Board
  • “Announcing the 7.0 release” → News
  • “Discussing tryton.community rules” → Message Board (assuming people want to discuss it here which is OK for me)
  • @edbo’s LDAP configuration issues and guide” → Message Board
  • “Announce about a GNU Health Job position” → Message Board
  • x2m new buttons” → Feature
  • “Change to the tryton.org website” → Communication

I’m missing an example about the Organization category. If this category is not really necessary just rename it to “Message Board”.

I’m proposing this rename because I understand that the proposal is to have a new category (named Message Board) for anything not releated to other categories.

“Add a new category for Message Board” → Organisation
“Call for election of the foundation board” → Organisation
“Creating a subgroup in heptapod for contributions” → Organisation

No, as the name implies, everything in that category is added by the community, where the name community can be used as wide as possible. Just like the name ‘organisation’ in the categories.

Well kick back :muscle: and rephrase Margaret Thatcher: ‘I want my Tryton.Community back!’ :laughing: Maybe call it ‘general resources’ or something because ‘message board’ seems a bit off here.

I hope the messages will stay right? I can imagine that some messages are move to other ‘official’ categories by moderators because they fit the right criteria.

It wasn’t about LDAP, but SAML. If Kerberos Authentication was merged I could have written about that as well.

I just mean that they are pushed at the bottom by new messages.

1 Like

What make this messages special that can not be included on Message Board or even on news?

For me the last two should be part of the news and not part of organization. The reason is because you are anouncing something to the public. Official announcement should be part of news so they get the proper visibility.

Even “Add a new category for message Board” should be part of “Ideas” because it wants to start a discussion but something that is not yet decided.

Because there is a more specific category in which they should go.

It could be discussed for the “Call for election”.

But “Create a subgroup” is clearly an organisational subject. Once the decision is made then it should be a news indeed.

Well it could be viewed that way, that’s why I said that your idea of having clear rules that will never fail won’t work. There is a lot of grey area when classifying discussions that we have to admit.

And, as I can see you coming, no having a “one category fits all and that’s all that we need” is not a good idea either.

No, that is not may idea. My idea is to have a clearer clasification about all of the categories and their usage.

I have some concers about:

I think the tryton forum should be as much inclusive as possible and we should encourage friendly non-offical projects (tryton.community and similars) to use our own forum. This way we can benefit for a more wide colaboration and even sometimes gather ideas for non official communities.

If you want to have some disctiontion about official and non-official organization, maybe we just need some tags?

Also what nor clear for me is where official statements should be placed. I had the impression that you want to use “Organization” for that but it is not still clear if that fit to news ot to organization. Maybe we should just need to have some not so important announcements that do not deserve an specific new but include them on the monthly newsletter. Of course we need to decide when a discussion is agreed and when to include them as official statement. I think it is important to do “Offical announcements” because I think there is some people not following the full discuss topic but following just tryton-announces.

For example:

Documentation update was not officialy announced:
Sponsoring was neither officially announced.
Development freeze and release dates are not also officialy announced once published.
If you have a look at the Organization category I’m sure you will find more examples.

To resume I think the proposal can be best described as:

  • Use organization category to discuss ideas on how to improve the project’s organization.
  • Use news to publish offical statements (using monthly newsletter when not so important).
  • Create a new “Message board” to include message that do not fit a better cattegory.

Of course, feel free to update/edit something if I did not understand properly.

Also it is not clear what for me if there should be an internal/external disctintion. We still need to agree on such part.

I kind of agree with this.

The only change I would make it that for me the “Organization” category is only related to tryton.org organization. I don’t think the new tryton.community or gnu health or whatever should discuss their own organization there. If they want to use the “Message Board” to do so, it’s OK but this category is for the Tryton project not its spin offs.

I don’t see how having a category that is dedicated to tryton.org is not inclusive if at the same time the discussion can be held somewhere else.

You could argue by saying that by using the “Message Board” category it’s considering them like second class citizen. But I disagree with that, this is the discourse forum for tryton.org and it’s obvious that some of the categories are focused only on tryton.org.

:+1: from my POV, official statements should indeed go either in News or the Monthly newsletter.

I think you resolved all my considers and I will be happy to move this topic forward.

I guess we need to create the new category and update the descriptions of the current Organization. Who is responsible for such procedure, do we need to leave some period for others to have some remarks?

Of course, it will be great to include such information on the organization category description.

Maybe we can also activate the resolve feature on the organization category so we will now that an agreement have been raised and once the topic is closed the creator (who made the proposal) must take the action (if any) to proceed with the agreement? Or do you have a better idea?

Make a proposal to be validated…

Resolve feature is to resolve problem. Discussion does not always have a resolution.
Also it will confuse with the support categories.

A proposal on what exactly?

I can not fully understand unless you finish the sentence.

If you do not want to have validation don’t make the proposal and just directly take the action. But in such case I guess we won’t find the best solution as colaboration normally improves the results.

Well if there is no resolution there is no action to take and nothing to announce.
I’m trying to find a way that the news teams knows what needs to be announced.
Do you have a better idea?

On updating and creating the descriptions.

Most of the organisation discussion has no point to go as a news.

But it must be communicated so anyone know how we are organized, everybody can follow the organization and where there is something un-organized everybody can fix it.

For example: I see a new label was created on the issue tracker but I do not know when I must use them or what does it mean when one of the issue gets such label.

I can understand there are some points that are not important enought to reserver a full news but luckly we have monthly newsletter to include them.

Here is the new category Message Board - Tryton Discussion