All, Created a ticket [1] to do this, made the change, and provided the patch. This process felt to be a bit much and was later echoed by Joe Witt. We had a bit of a conversation on the ticket about the correct course of action, and wanted to see what folks found to be the best path forward.
Personally, I am not a fan of tickets that can never be officially closed, which makes a single catch-all ticket suboptimal from my perspective. What do people wish to see? An issue per item? An issue that is left open and is the issue referenced for minor web site updates, with separate issues for larger changes such as themes and addition/removal of pages? Should minor changes get an associated issue for traceability but just bypass the whole review process? Last email about website issue tracking from me. Promise! ;) [1] https://issues.apache.org/jira/browse/NIFI-789 On Wed, Jul 22, 2015 at 8:17 AM, Joe Witt <[email protected]> wrote: > He asked off ipmc i believe. Pls just fix spelling > On Jul 22, 2015 5:08 AM, "Brandon DeVries" <[email protected]> wrote: > > > I think Benson actually asked off of the PMC[1], so he should probably > > just be removed from the list. > > > > (Obviously make sure I read that right. I have no desire to kick him out > > if he doesn't actually want out...) > > > > [1] > > > > > http://mail-archives.apache.org/mod_mbox/incubator-general/201507.mbox/%3CCALhtWkd6%2BwH%3DyAhOkD-X-7NC8J_7A-FmU8wzYgK%2BTiXG%2BwjF7A%40mail.gmail.com%3E > > > > On Wed, Jul 22, 2015 at 7:52 AM Dan Bress <[email protected]> > wrote: > > > > > If you are still working on this Aldrin, I noticed that Benson's name > is > > > spelled wrong on the people page [1] > > > bimargulies Benson Margulie > > > > > > [1]http://nifi.apache.org/people.html > > > > > > Dan Bress > > > Software Engineer > > > ONYX Consulting Services > > > > > > ________________________________________ > > > From: Joe Witt <[email protected]> > > > Sent: Tuesday, July 21, 2015 6:02 PM > > > To: [email protected] > > > Subject: Re: Web site fixes/corrections > > > > > > I think Sean's proposal is a good balance. We want it to be easy for > > > folks to contribute to making the website awesome-er. We have a good > > > start but we have a long way to go. For simple cleanup/maintenance > > > things a single cover-all JIRA should suffice. If someone wants to > > > work a new concept/page/theme then that should have its own ticket. > > > > > > On Tue, Jul 21, 2015 at 3:00 PM, Sean Busbey <[email protected]> > > wrote: > > > > I think a single "cleanup" jira that covers everything fixed in one > go > > > > would be good, but I know that I tend to fall on the > > jira-for-everything > > > > side of things. > > > > > > > > On Tue, Jul 21, 2015 at 4:56 PM, Aldrin Piri <[email protected]> > > > wrote: > > > > > > > >> All, > > > >> > > > >> I have made fixes to the website inclusive of items such as > correcting > > > >> broken links, typos, and the like and have never created issues for > > > these > > > >> fixes as I viewed them to be minor changes. > > > >> > > > >> I was curious if this practice seemed acceptable or if the community > > > >> preferred an issue for each such change. > > > >> > > > >> Thanks! > > > >> > > > > > > > > > > > > > > > > -- > > > > Sean > > > > > >
