Thanks all for the votes and comments. re:Jira - I hear and understand all questions about Jira not being the absolute best option, however I think the positive points are strong enough to still use is as primary option.
re: Taxonomy - The Project Management I refer to in #1 are more tasks like, clean-up Stale Jira tickets or ensure releases are on time. Therefore I would leave it as a separate option. Thanks all for your valuable comments, I'll proceed to implement this. G On Fri, 24 Aug 2018 at 12:09, Hadar Hod <[email protected]> wrote: > +1 > > On Fri, Aug 24, 2018 at 11:50 AM Henning Rohde <[email protected]> wrote: > >> +1 >> >> On Fri, Aug 24, 2018 at 11:44 AM Rose Nguyen <[email protected]> wrote: >> >>> +1 Great idea >>> >>> On Fri, Aug 24, 2018 at 10:01 AM Mikhail Gryzykhin <[email protected]> >>> wrote: >>> >>>> +1. Idea sounds great. >>>> >>>> --Mikhail >>>> >>>> Have feedback <http://go/migryz-feedback>? >>>> >>>> >>>> On Fri, Aug 24, 2018 at 7:19 AM Maximilian Michels <[email protected]> >>>> wrote: >>>> >>>>> +1 Code is just one part of a successful open-source project. As long >>>>> as >>>>> the tasks are properly labelled and actionable, I think it works to >>>>> put >>>>> them into JIRA. >>>>> >>>>> On 24.08.18 15:09, Matthias Baetens wrote: >>>>> > >>>>> > I fully agree and think it is a great idea. >>>>> > >>>>> > I think that, next to visibility and keeping track of everything >>>>> that is >>>>> > going on in the community, the other goal would be documenting best >>>>> > practices for future use. >>>>> > >>>>> > I am also not sure, though, if JIRA is the best place to do so, as >>>>> > Austin raised. >>>>> > Introducing (yet) another tool on the other hand, might also not be >>>>> > ideal. Has anyone else experience with this from other Apache >>>>> projects? >>>>> > >>>>> > On Fri, 24 Aug 2018 at 06:04 Austin Bennett < >>>>> [email protected] >>>>> > <mailto:[email protected]>> wrote: >>>>> > >>>>> > Certainly tracking and managing these are important -- though, is >>>>> > Jira the best tool for these things? >>>>> > >>>>> > I do see it useful to put in Jira tickets in for my director to >>>>> have >>>>> > conversations on specific topics with people, for consensus >>>>> > building, etc etc. So, I have seen it work even for non-coding >>>>> tasks. >>>>> > >>>>> > It seems like much of #s 2-6 mentioned requires project >>>>> management >>>>> > applied to those specific domains and is applicable elsewhere, >>>>> > wondering what constitutes "pure" project management in #1 (as it >>>>> > applies here)...? In that light I'm just getting picky about >>>>> > taxonomy :-) >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > On Thu, Aug 23, 2018 at 3:10 PM Alan Myrvold < >>>>> [email protected] >>>>> > <mailto:[email protected]>> wrote: >>>>> > >>>>> > I like the idea of recognizing non-code contributions. These >>>>> > other efforts have been very helpful. >>>>> > >>>>> > On Thu, Aug 23, 2018 at 3:07 PM Griselda Cuevas < >>>>> [email protected] >>>>> > <mailto:[email protected]>> wrote: >>>>> > >>>>> > Hi Beam Community, >>>>> > >>>>> > I'd like to start tracking non-code contributions for >>>>> Beam, >>>>> > specially around these six categories: >>>>> > 1) Project Management >>>>> > 2) Community Management >>>>> > 3) Advocacy >>>>> > 4) Events & Meetups >>>>> > 5) Documentation >>>>> > 6) Training >>>>> > >>>>> > The proposal would be to create six boards in Jira, one >>>>> per >>>>> > proposed category, and as part of this initiative also >>>>> clean >>>>> > the already existing "Project Management" component, i.e. >>>>> > making sure all issues there are still relevant. >>>>> > >>>>> > After this, I'd also create a landing page in the website >>>>> > that talks about all types of contributions to the >>>>> project. >>>>> > >>>>> > The reason for doing this is mainly to give visibility to >>>>> > some of the great work our community does beyond code >>>>> pushes >>>>> > in Github. Initiatives around Beam are starting to spark >>>>> > around the world, and it'd be great to become an Apache >>>>> > project recognized for our outstanding community >>>>> recognition. >>>>> > >>>>> > What are your thoughts? >>>>> > G >>>>> > >>>>> > Gris >>>>> > >>>>> > -- >>>>> >>>>> -- >>>>> Max >>>>> >>>> >>> >>> -- >>> >>> >>> Rose Thi Nguyen >>> >>> Technical Writer >>> >>> (281) 683-6900 >>> >>
