I appreciate Ross's concern. I have a companion one. Bottom line, I would be very discouraged if manual use were excluded.
- Dennis RELATED THOUGHTS The greatest source of issues and concerns and also some interest in how to help for Apache OpenOffice is end-users and some inexperienced developers. For them, issue trackers are not the first thing thought of and, out of ineptness, their efforts are often rebuffed. Now, AOO uses bugzilla for worthy historical reasons but I don't think JIRA would be that much easier for end-users, especially since the fact that there is really only one JIRA there can be very confusing for novices and users having an urgent-for-them problem. These concerns are probably orthogonal to HW (and somewhat for GSoC too). But I think a companion use of HW by a project having a wide variety of tasks with quite diverse skill requirements, and an offer of some degree of mentoring is very worthwhile. I am not objecting to scanning of JIRAs for HW items, although it might be better for them to have a help-wanted tag, among others, since one might want to slant things appropriate to appearance on HW and have the label affixed with some degree of forethought. > -----Original Message----- > From: Ross Gardler [mailto:ross.gard...@microsoft.com] > Sent: Monday, February 8, 2016 10:41 > To: dev@community.apache.org > Subject: RE: Help Wanted! (it's a title, not a request!) > > This is great, but... > > The success of something like this is not in the tool, it's in the > content. > > I worry that by requiring projects to enter the data separately to their > chosen issue tracker we are reducing the chances of this succeeding (and > it deserves to succeed as a tool). Furthermore, when it comes around to > GSoC projects across the foundation already mark tasks as "mentor". > > I hear the concern that some projects use Bugzilla, but the majority use > Jira. > > Can we do imports from Jira, filtered by the "mentor" label? > > Ross > > -----Original Message----- > From: Daniel Gruno [mailto:humbed...@apache.org] > Sent: Monday, February 8, 2016 3:38 AM > To: dev@community.apache.org > Subject: Re: Help Wanted! (it's a title, not a request!) > > On 02/08/2016 12:36 PM, Maxim Solodovnik wrote: > > Hello Daniel, > > > > Could you please describe a bit how JIRA issues are selected to be > > displayed? > > this [1] query return no results :(( > > > > [1] > > https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fhelpw > > anted.apache.org%2flistitems.lua%3fproject%3dopenmeetings&data=01%7c01 > > %7cRoss.Gardler%40microsoft.com%7c0d06626ee77b454e4b3a08d3307c5fbd%7c7 > > 2f988bf86f141af91ab2d7cd011db47%7c1&sdata=yQQSTsTOXuZ5oHv4dAyz1yIOmBCY > > R49X0zNf3N2r4pQ%3d > > > > It doesn't quite work that way. The whole issue here is that there is no > way to uniformly do this via JIRA or BugZilla, as they don't quite have > these sort of information fields, so this is an 'aside' to it. > > You have to add the tasks by clicking on the 'add/edit tasks' link at > the top of the front page, and then they'll show up. You can of course > link to a JIRA ticket inside the task. > > With regards, > Daniel. > > > > > On Mon, Feb 8, 2016 at 4:56 PM, Daniel Gruno <humbed...@apache.org> > wrote: > > > >> On 02/08/2016 11:53 AM, Francesco Chicchiriccò wrote: > >>> Just to show my appreciation: +1, looks very cool! > >>> > >>> Any idea of when we can start filling it up with real things? > >>> Thanks. > >> > >> I've already started deleting the test entries, so you could start > >> using it already if you like. I'll remove the warnings from the front > >> page then > >> :) > >> > >> With regards, > >> Daniel. > >> > >>> > >>> Regards. > >>> > >>> On 07/02/2016 17:01, Daniel Gruno wrote: > >>>> Hi ComDev folks! Ramblings incoming :) > >>>> > >>>> As an aside to the 'Guiding volunteers' thread, I was talking with > >>>> Rich > >>>> (Bowen) while he was at DevConf this weekend, and we got to > >>>> thinking whether it was possible to make a tiny tool that would > >>>> solve one specific issue we often come across when someone says "I > >>>> know X, Y and Z > >>>> - What can I do to help Apache?". > >>>> > >>>> Traditionally, we've said "subscribe to our mailing list (which > one?!)" > >>>> or "Go look at JIRA/BugZilla", which in itself is fine, but > >>>> off-putting to many people as we don't actively use neither MLs or > >>>> bug trackers to advertise what we want done, and what tech/person > >>>> skills would be helpful where (we're terrible!). Furthermore, it is > >>>> our opinion/assessment that bug trackers are not that great from a > >>>> "skills > >>>> -> tasks" perspective. While great for bugs and larger tasks for an > >>>> existing audience, they don't provide the right overview or search > >>>> features that one could want, and keeping some sort of uniform > >>>> setup for these tasks across the ASF is going to be a LOT of work. > >>>> > >>>> ...If only we had somewhere someone could just go and say "I'm > >>>> great at marketing and documentation, what tasks are there that I > >>>> can do?" and then get 10 different requests across 6 projects, some > >>>> that you could start on right away and some that require more > >>>> intimate knowledge with the project. > >>>> > >>>> ...Or the experienced C/Python programmer that wants to know which > >>>> tasks at Apache they could hack on as a good introduction to that > >>>> project, while at the same time helping the project accomplish > something new. > >>>> > >>>> ...Oh, and wouldn't it be nifty if we could have a widget we could > >>>> place on our web site that lists what we as a project or foundation > >>>> are looking for right now in terms of work to be done, so when > >>>> people visit our page, they can see that "hey, we're looking for a > >>>> web dev guru - is that you?" ? > >>>> > >>>> Enter 'Help Wanted!'. It's a very small (and very much > >>>> work-in-progress) tool that you can use to browse the tasks that > >>>> all the Apache projects would like to get done, see the difficulty > >>>> of it, language (whether spoken/written or programming) skills > >>>> needed, what it's about and who/how to contact. You can also use > >>>> the HW widget to plug your own project's requests into your web > >>>> site, or you can display all the current tasks waiting in the > >>>> system across the ASF. 350+ initiatives, > >>>> 170+ TLPs, one uniform hub for requests that can help people get > >>>> 170+ started > >>>> with Apache. > >>>> > >>>> The code is "live" at: > >>>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fhe > >>>> lpwanted.apache.org%2f&data=01%7c01%7cRoss.Gardler%40microsoft.com% > >>>> 7c0d06626ee77b454e4b3a08d3307c5fbd%7c72f988bf86f141af91ab2d7cd011db > >>>> 47%7c1&sdata=BR%2b5amxjv78yRbve0XYu%2f5ATbzqcyrJNnxCAP6G4TAI%3d > >>>> A test widget is here: > >>>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fhe > >>>> lpwanted.apache.org%2fwtest.html&data=01%7c01%7cRoss.Gardler%40micr > >>>> osoft.com%7c0d06626ee77b454e4b3a08d3307c5fbd%7c72f988bf86f141af91ab > >>>> 2d7cd011db47%7c1&sdata=k4nYUB8PION8XOaisK2k0OvMYXCvhTXyY79ScjYoUS4% > >>>> 3d (the test widget shows what it could look like on the httpd > >>>> site) > >>>> > >>>> It's open for all committers to go set up new tasks (universal > >>>> commit bit, so to speak, just click on 'edit tasks'), and we hope > >>>> it will be a hub for putting people on the right path - whether > >>>> that be a pointer to JIRA, ML etc - to contributing to our > >>>> projects. Or it'll crash and burn and we'll never speak of it again > >>>> :) > >>>> > >>>> Contributions, feedback, quality control etc are MOST WELCOME, and > >>>> we're only getting started with the proof-of-concept right now (as > >>>> found in svn). Hopefully we'll have something stable and polished > >>>> by the end of February? :) > >>>> > >>>> With regards, > >>>> Daniel. > >>>> > >>>> > >>>> PS: Yes, I know the admin area is a stylistic nightmare. That'll be > >>>> fixed...eventually! And the task guide needs a LOT of work. Saying > >>>> "contact the dev list" isn't enough, but I'll need a word smith for > >>>> that :) > >>>> > >>> > >>> > >> > >> > > > >
