Re: project infrastructure

On Wed, 23 Nov 2011 19:20:23 -0500 (EST), Will Kahn-Greene wrote:

A bit lateish, but I have no strong opinions on gitorious vs github (I
think keeping the repo at gitorious would be fine). But I am always for
hosting things at existing infrastructure, relieving you from the burden
of maintaining that. So using some bug tracker at github, assembla or
whereever, sounds good to me. github or gitorious? ppff, it's just a
different git@ URL 

Sebastian

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d

_______________________________________________
Pyblosxom-devel mailing list
Pyblosxom-devel@...
https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel

Re: project infrastructure

On Thu, 01 Dec 2011 16:25:18 +0100
Sebastian Spaeth <Sebastian@...> wrote:

> github or gitorious? ppff,
> it's just a different git@ URL 
> 

I know you meant that as a joke, but seriously, github and gitorious are quite different.
personally i find gitorious very hard to navigate, their UI/menus aren't very well thought out.

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d

_______________________________________________
Pyblosxom-devel mailing list
Pyblosxom-devel@...
https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel

Re: project infrastructure

> 1. Move from gitorious to github.  In doing this, we gain post-commit 
> hooks some of which are wildly useful, an issue tracker, inline comments 
> for pull requests, probably an order of magnitude more people who already 
> have github accounts and who are used to drive-by-fixes, and probably some 
> other github features I haven't yet discovered.

Github can host the project website for you as well, and a wiki.

The one disadvantage is that it's not open source whereas gitorious is.
Hosting your git repo on github doesn't tie you down to anything as you
can always move it somewhere else if you want to. But the more you come
to depend on github's extra features like the issue tracker, the wiki,
etc., the more you're becoming dependent on a proprietary platform.

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d

Re: project infrastructure

On Fri 02 Dec 2011 01:05:57 PM EST, seanh wrote:
>> 1. Move from gitorious to github.  In doing this, we gain post-commit 
>> hooks some of which are wildly useful, an issue tracker, inline comments 
>> for pull requests, probably an order of magnitude more people who already 
>> have github accounts and who are used to drive-by-fixes, and probably some 
>> other github features I haven't yet discovered.
>
> Github can host the project website for you as well, and a wiki.
>
> The one disadvantage is that it's not open source whereas gitorious is.
> Hosting your git repo on github doesn't tie you down to anything as you
> can always move it somewhere else if you want to. But the more you come
> to depend on github's extra features like the issue tracker, the wiki,
> etc., the more you're becoming dependent on a proprietary platform.

I dig what you're saying.  I definitely don't want to repeat another SF 
situation--that sucked.

I currently plan to use github for code, the issue tracker, and patch 
workflow.  We can trivially move the code elsewhere.  The patch 
workflow is transient, so if we move elsewhere we'll lose that and 
change workflows.

That brings us to the issue tracker.  I'm pretty ok with ditching 
issues in one system and moving to a new system.  More often than not, 
issues that languish are either fixed, uninteresting, not fleshed out 
or in some state where ditching it isn't a big deal.  I don't want this 
project to accrue task-debt.  We either work on things we're interested 
in, or we don't.  The set of issues we're interested in working on 
changes.  If I had my druthers, I'd have our bug system auto-expire 

Re: project infrastructure

On Fri, 02 Dec 2011 13:23:03 -0500
will kahn-greene <willg@...> wrote:

> Given that, switching to the github issue tracker is fine
> and doesn't lock us in.

GH issues doesn't lock us in? is that a typo or am i missing something?

> I don't want to use Trac, Roundup

what's wrong with roundup?

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d

Re: project infrastructure

On Fri 02 Dec 2011 01:37:08 PM EST, Dieter Plaetinck wrote:
> On Fri, 02 Dec 2011 13:23:03 -0500
> will kahn-greene <willg@...> wrote:
>
>> Given that, switching to the github issue tracker is fine
>> and doesn't lock us in.
>
> GH issues doesn't lock us in? is that a typo or am i missing something?

You removed the context for that statement in your reply.  It doesn't 
lock us in because I don't really care about leaving issues if we 
switch trackers.

>> I don't want to use Trac, Roundup
>
> what's wrong with roundup?

Pretty sure I've talked about this already, but I'm game for iterating 
through it again.

Roundup doesn't have milestones by default.  I've added mediocre 
milestone stuff based on the original round of milestone stuff that 
Jack at OpenHatch did.  However, the urls for milestones are awful and 
generally I find the ui to be problematic.  There are bugs in Roundup 
that irritate me.  One of them is that the ExportCSV action doesn't 
check the querystring _before_ writing stuff to output.  So when it 
hits a problem, it's already written stuff to output and thus you get 
back an HTTP 200 response with gibberish in it.  The problem there is 
that Google bot and other search engines for some reason put bad stuff 
in the querystring and thus I get a ton of error emails.  I tried to 

Re: project infrastructure

I know both well...  what I implied is that the git repo is essentially the same. I hardly ever view the web
ui of my githhub projects, and you can always mix with better infrastructure, ie bug trackers from
assembla.com or whatnot.
That having said, github is certainly cool.
Sebastian

>> github or gitorious? ppff,
>> it's just a different git@ URL 
>> 
>
>I know you meant that as a joke, but seriously, github and gitorious
>are quite different.
>personally i find gitorious very hard to navigate, their UI/menus
>aren't very well thought out.

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d

1.5 status -- anything more to do?

I worked through the remaining bugs sitting in the 1.5 milestone today. 
Now there are no more bugs sitting in the 1.5 milestone.

If there's anything outstanding that I haven't finished up, let me know in 
the next two days.  Barring any issues, I'm going to ship 1.5 next week.

After 1.5 goes out, I'm going to spend some time moving interesting bugs 
to the issue tracker on github and then take a hiatus from Pyblosxom 
development for a while.  I will continue to work through patches 
submitted by other people whether they code or docs or fixes to the 
website.

/will

------------------------------------------------------------------------------
Learn Windows Azure Live!  Tuesday, Dec 13, 2011
Microsoft is holding a special Learn Windows Azure training event for 
developers. It will provide a great way to learn Windows Azure and what it 
provides. You can attend the event by watching it streamed LIVE online.  
Learn more at http://p.sf.net/sfu/ms-windowsazure

Re: 1.5 status -- anything more to do?

Anything is fine by me.  Patches sent to the mailing list, pull requests 
on github, issues on github with comments on how to fix the issue, pinging 
me on IRC, ...

On Sat, 17 Dec 2011, Akai wrote:
> 
> What would be the best way to contribute post-hiatus?
>
> On 12/17/2011 5:17 PM, Will Kahn-Greene wrote:
>> I worked through the remaining bugs sitting in the 1.5 milestone today.
>> Now there are no more bugs sitting in the 1.5 milestone.
>> 
>> If there's anything outstanding that I haven't finished up, let me know in
>> the next two days.  Barring any issues, I'm going to ship 1.5 next week.
>> 
>> After 1.5 goes out, I'm going to spend some time moving interesting bugs
>> to the issue tracker on github and then take a hiatus from Pyblosxom
>> development for a while.  I will continue to work through patches
>> submitted by other people whether they code or docs or fixes to the
>> website.
>> 
>> /will
>>
>> 
>> ------------------------------------------------------------------------------
>> Learn Windows Azure Live!  Tuesday, Dec 13, 2011
>> Microsoft is holding a special Learn Windows Azure training event for
>> developers. It will provide a great way to learn Windows Azure and what it
>> provides. You can attend the event by watching it streamed LIVE online.