Looking for something to hack on?

[Moritz Lenz]

On 10/17/2011 06:42 PM, Jonathan "Duke" Leto wrote:
> Just to be clear, I am not talking about a wholesale migration. I will just
> simply not use Trac for new tickets and will suggest that others do the same.

So we have two bug trackers to ignor^Wtend.

> Instead, issues in the appropriate repo on Github will be created. If somebody
> cares enough about a TT, it will get migrated to a Github issue.

So we ignore the effort that people put into reporting bugs, and tell
them "if you care, do more work for us". If you ever asked yourself why
parrot doesn't have many users, think again.

That way you only encourage potential users to write hateful blog posts
about parrot, you don't encourage them to tell the developers what goes
wrong.

> I don't want to hear strawman arguments about how I don't care about all the
> hardwork that people have put into our TTs. I have created and cagecleaned many
> TT's. 

How about non-strawman arguments? What do you say to users who put a lot
of effort into submitting good bug reports, and which will got lost by
the non-migration?

> But the simple fact is that we, Parrot hackers, need to refactor our
> community infrastructure if we hope to continue.

Yes, parrot needs to do things better, but it needs a plan and a
direction. A single developer dashing off and calling it a "community
refactor" isn't a plan.

> "Do what you have always done, get what you have always gotten".
> 
> Parrot is losing developers and quickly becoming even more irrelevant, and I
> refuse to just rearrange furniture on the deck of a sinking ship.

Sorry, but it sounds like exactly what you are doing. You're not fixing
the deep issues with parrot (slow calling conventions, no JIT compiler,
very limited NCI, ...), you're rearranging furniture.

> Trac actively discourages new developers, since we have to lock it down from
> Trac spam. Github actively encourages new developers via all the social
> features. If we want to continue, we need to fully embrace Github.

How about fixing trac? Maybe by using github for authentication as an
option?

Jonathan, I can't tell you what to do, but so far I got the impression
that you are running towards a shiny new feature without consulting the
rest of the community, and a weak rationalization after the fact.

The reason I have a problem this time is that you place a burden on
others, either by forcing them to consider two bug trackers, or by
forcing them to migrate tickets, or by condemning the non-migrated
tickets to go unnoticed eventually.

Please think again if that's what you want, and if really considered the
costs and possible alternatives.

Cheers,
Moritz