Re: Bug tracking & triaging proposal

polyester <paula-fsXTdVcv1GdrovVCs/[email protected]>
Newsgroups gmane.comp.web.zope.plone.devel
Message-ID <[email protected]>
On 02-08-14 11:06, Dylan Jay wrote:
> BTW, if github is going ahead anyway (which I see little advantage) the
> most appropriate package I would have thought was buildout.coredev since
> that's where milestones and version really live.
> 

from an approachability/documentation/end-user perspective, that's not
exactly where I'd like to point people to, as it clearly signals "stay
out unless you're very sure what you're doing".

but that's exactly why I'd like this to be discussed at a FWT meeting
with guests, so that the different perspectives can be honored.

A bunch of scripts and tools exist, btw, to move issues between repos.
Not in the github webinterface, but via the API it's no problem. Also
tools to turn the issues in a more kanban-like view, for those that
prefer that.

I would be in favour also of the Plone metapackage, like Asko suggested,
but that's just one viewpoint.

The drawback that you'll need a github account to file a ticket is
offset for me by:

- we'll actually be able to link and close tickets by pull requests
- we'll be able to actually reach the people who filed tickets
- the amount of non-spam anonymous tickets is minimal, and most of those
are not really anonymous at all; people write their name under it, but
just forget to login.



paul


------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.