Select project management/collaboration tools about forest HOT 9 CLOSED

That makes me much happier 🔥

from forest.

@rjpower4 Did you create a forest developer team? I thought I saw that in an email, but don't see it listed on the page.

from forest.

Also @rjpower4 What do you think about this overall workflow that keeps everything within the GitHub ecosystem? Do you see anything missing from here?

from forest.

Couple of notes:

• I don't think we should attach version numbers to the milestones other than v1.0.0 as this conflates two levels of semantic meaning: high-level associated with project goals and a lower-level version associated with features added/APIs broken
• I have created a "leads" team, it is here, do you want a general developer team?
• I would advise doing general discussions in discussions
• Announcements for the developer team could go in that lower-level team if we want or put them in discussions

from forest.

• I don't think we should attach version numbers to the milestones other than v1.0.0 as this conflates two levels of semantic meaning: high-level associated with project goals and a lower-level version associated with features added/APIs broken

Maybe this isn't a great motivation, but I added numbers in because grouping by milestone on the GitHub Projects page occurs alphabetically, and I wanted it in that chronological order to keep track of things - so putting numbers in clarifies what order they go in. I agree it's a bit awkward. I can look into if any other options work for the management side of things.

from forest.

Having a general developers team I think is a good idea so we can put announcements and whatnot there, separate from the discussions board

from forest.

• I don't think we should attach version numbers to the milestones other than v1.0.0 as this conflates two levels of semantic meaning: high-level associated with project goals and a lower-level version associated with features added/APIs broken

Maybe this isn't a great motivation, but I added numbers in because grouping by milestone on the GitHub Projects page occurs alphabetically, and I wanted it in that chronological order to keep track of things - so putting numbers in clarifies what order they go in. I agree it's a bit awkward. I can look into if any other options work for the management side of things.

Maybe just number them?

from forest.

Maybe just number them?

Done. Does that work for you?

from forest.

Since this is mostly done now, I'm going to move the remaining items into separate issues

from forest.