python-markdown-discuss

[Python-markdown-discuss] git and gitorious

[Yuri T. <qar...@gm...>]

Waylan's patch reminded me of something I wanted to bring up: should we
consider moving from SF's subversion to something a tiny little bit less
sucky?  I recently moved Sputnik over to a git repository hosted by
gitorious.org and I since can't stop telling people how much in love I am
with both git and gitorious.  I wake up in the morning and look forward to
the day knowing that if someone emails me a patch it will be in form of a
link to something like:

http://gitorious.org/projects/sputnik/repos/mainline/commits/3028915518ebdc0574bf3255f2ffa48c82e395eb

And that it would then take me no time to integrate it, even if my own code
has moved on.

There is also a nice open-sourcy thing about gitorious (and git more
generally), in that people don't need my permission to start making clones
and commits (into their clones).  They just need to email me a list of
commits later.  Click around the Sputnik gitorious repository and compare
this with what we have now:

Gitorious: http://gitorious.org/projects/sputnik/
SF:  http://python-markdown.svn.sourceforge.net/viewvc/python-markdown/

 - yuri

-- 
http://sputnik.freewisdom.org/

Re: [Python-markdown-discuss] git and gitorious

[Waylan L. <wa...@gm...>]

I've only heard good things about git and have been meaning to play
with it. At this point I'd be happy with pretty much anything but
sourceforge. I was going to object because we need a bug tracker, but
I see you have that working in sputnik. Would you be setting that up
for python-markdown as well? If so, that would only leave the list.
Would we use Google Groups or something, or leave it as is?

On Mon, Mar 24, 2008 at 8:36 PM, Yuri Takhteyev <qar...@gm...> wrote:
> Waylan's patch reminded me of something I wanted to bring up: should we
> consider moving from SF's subversion to something a tiny little bit less
> sucky?  I recently moved Sputnik over to a git repository hosted by
> gitorious.org and I since can't stop telling people how much in love I am
> with both git and gitorious.  I wake up in the morning and look forward to
> the day knowing that if someone emails me a patch it will be in form of a
> link to something like:
>
> http://gitorious.org/projects/sputnik/repos/mainline/commits/3028915518ebdc0574bf3255f2ffa48c82e395eb
>
> And that it would then take me no time to integrate it, even if my own code
> has moved on.
>
> There is also a nice open-sourcy thing about gitorious (and git more
> generally), in that people don't need my permission to start making clones
> and commits (into their clones).  They just need to email me a list of
> commits later.  Click around the Sputnik gitorious repository and compare
> this with what we have now:
>
> Gitorious: http://gitorious.org/projects/sputnik/
> SF:  http://python-markdown.svn.sourceforge.net/viewvc/python-markdown/
>
>  - yuri
>
> --
> http://sputnik.freewisdom.org/
> -------------------------------------------------------------------------
>  This SF.net email is sponsored by: Microsoft
>  Defy all challenges. Microsoft(R) Visual Studio 2008.
>  http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
>  Python-markdown-discuss mailing list
>  Pyt...@li...
>  https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss
>
>



-- 
----
Waylan Limberg
wa...@gm...

Re: [Python-markdown-discuss] git and gitorious

[Yuri T. <qar...@gm...>]

> I see you have that working in sputnik. Would you be setting that up
> for python-markdown as well? If so, that would only leave the list.
> Would we use Google Groups or something, or leave it as is?
>

I could.  As for the list, it's not like it needs to be all or nothing.  We
could just keep the list on SF.  We could even keep the bug tracker there
for now.

For others: the Sputnik bug tracker that Waylan is referring to is
http://sputnik.freewisdom.org/en/Tickets  It's a bit rought around the
edges, but has a plus of being integrated into the wiki and I want to try to
intergrate it with git, so that it would be possible to put Markdown into
the commit messages and into tickets: things like  "Fixes
[[Tickets/0000089]]" into commits and "I _tried_ to fix it with
[[Commits/503623b]] but this wasn't enough" into tickets.  Just waiting for
a few other pieces to be finished.  (Of course, this integration with git
will only work when looking at commits that are mounted onto the wiki - not
when looking at them on gitorious.)  Same with the list messages: see
[[List/git and gitorious]]  Anyway, that's a different project, so you don't
all need to convert to Sputnikism.  We don't even need to use Sputnik at
all.  I've been using it as a stop gap measure until infogami is released,
mostly because (1) it uses Markdown and (2) it was easy for me to install
it.

 - yuri




-- 
http://sputnik.freewisdom.org/

Re: [Python-markdown-discuss] git and gitorious

[Waylan L. <wa...@gm...>]

On Mon, Mar 24, 2008 at 9:48 PM, Yuri Takhteyev <qar...@gm...> wrote:
>
>
> > I see you have that working in sputnik. Would you be setting that up
> > for python-markdown as well? If so, that would only leave the list.
> > Would we use Google Groups or something, or leave it as is?
> >
> >
>
> I could.  As for the list, it's not like it needs to be all or nothing.  We
> could just keep the list on SF.

That wouldn't bother me to much. I rarely interact with the list other
than from my email client. But it would be nice to be completely rid
of SF.

> We could even keep the bug tracker there
> for now.

Actually, this is the part that I want to be rid of the most. I hate
using the SF bug tracker. Pretty much anything else would be better.
While better version control of the source is nice to have, IMO a
better bug tracker is necessary.



-- 
----
Waylan Limberg
wa...@gm...

Re: [Python-markdown-discuss] git and gitorious

[David W. <wo...@cs...>]

I certainly wouldn't complain about moving to a DVCS :)

Now, if I had my way, it would be bzr+Launchpad... But, since I don't  
want my way badly enough to orchestrate any sort of large-scale  
changes, I won't complain too loudly ;)

On 24-Mar-08, at 8:36 PM, Yuri Takhteyev wrote:

> Waylan's patch reminded me of something I wanted to bring up:  
> should we consider moving from SF's subversion to something a tiny  
> little bit less sucky?  I recently moved Sputnik over to a git  
> repository hosted by gitorious.org and I since can't stop telling  
> people how much in love I am with both git and gitorious.  I wake  
> up in the morning and look forward to the day knowing that if  
> someone emails me a patch it will be in form of a link to something  
> like:
>
> http://gitorious.org/projects/sputnik/repos/mainline/commits/ 
> 3028915518ebdc0574bf3255f2ffa48c82e395eb
>
> And that it would then take me no time to integrate it, even if my  
> own code has moved on.
>
> There is also a nice open-sourcy thing about gitorious (and git  
> more generally), in that people don't need my permission to start  
> making clones and commits (into their clones).  They just need to  
> email me a list of commits later.  Click around the Sputnik  
> gitorious repository and compare this with what we have now:
>
> Gitorious: http://gitorious.org/projects/sputnik/
> SF:  http://python-markdown.svn.sourceforge.net/viewvc/python- 
> markdown/
>
>  - yuri
>
> -- 
> http://sputnik.freewisdom.org/
> ---------------------------------------------------------------------- 
> ---
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ 
> _______________________________________________
> Python-markdown-discuss mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss