Organization / Confusion

[Dustin]

Can we figure out how to organize ourselves a bit more? I feel like
there's some duplication of effort.

We've got three places for downloads, a few repositories (at least
two toplevel git repos and a mercurial repo), two places to file bugs,
a couple wikis, etc...

I fixed the bug that was just reported in google code before it was
reported. I had one bug filed against my project that was installer
specific and I believe I've fixed that.

I'd love it if we could all work together to get ZFS working as well
as it was under Leopard.

[Silas Baronda]

Maybe chatting on IRC?
#mac-zfs on freenode.org is clear.

[Alex Blewitt]

On 24 Oct 2009, at 00:10, Dustin wrote:

> I fixed the bug that was just reported in google code before it was
> reported. I had one bug filed against my project that was installer
> specific and I believe I've fixed that.

Right, I wanted to put it there to (a) document that the current
binaries were 32-bit only (in case others pick this up) and that (b)
it was being worked on/fixed.

> I'd love it if we could all work together to get ZFS working as well
> as it was under Leopard.

Yup, sounds like a good goal :-)

> We've got three places for downloads, a few repositories (at least
> two toplevel git repos and a mercurial repo), two places to file bugs,
> a couple wikis, etc...

The downloads on http://code.google.com isn't really usable, since
it's a CDDL specific thing, that's why I went with moving it to the
mailing list's public files. However, it has a good wiki and issue
tracker, and can easily create links to various places. Plus, it's
fairly easy to delegate out permissions for others who want to join in.

As for the repositories; the git import (by peaceful) is great,
because it contains all the SVN information and history. That might be
useful when it comes to (attempting to) merge in things from future
versions of ZFS. And one of the benefits of git (or distributed file
systems generally) is that there are expected to be multiple versions.
One can fairly easily pull/push versions from one to another, after
all. It also means that there's no master repository per se; that's a
bit confusing for end users but we'll probably be able to find out
who's going to move it forwards and base it on there.

What other bug filing places are there? Or wikis, for that matter ...

Alex

[Dustin]

On Oct 23, 4:17 pm, Alex Blewitt <alex.blew...@gmail.com> wrote:

> Right, I wanted to put it there to (a) document that the current  
> binaries were 32-bit only (in case others pick this up) and that (b)  
> it was being worked on/fixed.

Yeah. Just pointing out that only one person seems to have access
to that site so far and I've closed a bug on mine already. I'd be
happy to give up my bug tracker for yours.


> The downloads onhttp://code.google.comisn't really usable, since  

> it's a CDDL specific thing, that's why I went with moving it to the  
> mailing list's public files. However, it has a good wiki and issue  
> tracker, and can easily create links to various places. Plus, it's  
> fairly easy to delegate out permissions for others who want to join in.

I don't quite understand the download issue there. I can use github
for that otherwise.

> As for the repositories; the git import (by peaceful) is great,  
> because it contains all the SVN information and history.

Yeah, that's the (at least) second one that I've seen. I've done
some work in mine (and should get bonus points for the umlaut on
Nöel.) :)

> That might be  
> useful when it comes to (attempting to) merge in things from future  
> versions of ZFS. And one of the benefits of git (or distributed file  
> systems generally) is that there are expected to be multiple versions.  

This is correct, but only when they share a root. I.e. these two
trees will not be compatible for most types of sharing.

> One can fairly easily pull/push versions from one to another, after  
> all. It also means that there's no master repository per se; that's a  
> bit confusing for end users but we'll probably be able to find out  
> who's going to move it forwards and base it on there.

Believe me I'm well versed in github (105 repos under my account,
and a couple other accounts) and git (I wrote little bits of it).

I'm all for decentralization, but I'd like it to work easily if
possible.

> What other bug filing places are there? Or wikis, for that matter ...

Github repos by default. I got a bug filed there, started a wiki
page to bring in the old Apple stuff, and have downloads.

Happy to get the stuff consolidated in such a way that won't cause
long-term problems.

[Alex Blewitt]

On 24 Oct 2009, at 00:24, Dustin wrote:

On Oct 23, 4:17 pm, Alex Blewitt <alex.blew...@gmail.com> wrote:

Right, I wanted to put it there to (a) document that the current  

binaries were 32-bit only (in case others pick this up) and that (b)  

it was being worked on/fixed.

Yeah.  Just pointing out that only one person seems to have access
to that site so far and I've closed a bug on mine already.  I'd be
happy to give up my bug tracker for yours.

The reason for creating it was really to have a central place for issue tracker items, wiki pages and the like. GitHub's good for code sharing and patches, but can make finding the info a bit more difficult. 

I posted earlier (http://groups.google.com/group/zfs-macos/browse_thread/thread/7db6ece8b24dba40) and am happy to include many others in it too - just let me know. Same goes for anyone else who wants to move this project forwards :-)

The downloads onhttp://code.google.comisn't really usable, since  

it's a CDDL specific thing

I don't quite understand the download issue there.  I can use github
for that otherwise.

Google Code doesn't officially recognise CDDL, so we can't post source/binaries there. I dumped them in the mailing list's 'files' section because thought anyone who has access to this list will have access to the files as well (http://groups.google.com/group/zfs-macos/files). Can we put the new build in there, if people are happy with it?

Yeah, that's the (at least) second one that I've seen.  I've done
some work in mine (and should get bonus points for the umlaut on
Nöel.) :)

I'd go with bonus points for the umlauts :-)

That might be useful when it comes to (attempting to) merge in things from future  

versions of ZFS. And one of the benefits of git (or distributed file  

systems generally) is that there are expected to be multiple versions.  

 This is correct, but only when they share a root.  I.e. these two
trees will not be compatible for most types of sharing.

I was thinking if we could find a way of diffing against r72, we could then work forwards. But it'd still be a bunch of work.

What other bug filing places are there? Or wikis, for that matter ...

 Github repos by default.  I got a bug filed there, started a wiki
page to bring in the old Apple stuff, and have downloads.

Didn't know github had a bug tracker. I'm fairly new to that :-) I copied over what I could find to the Google Code wiki pages (http://code.google.com/p/maczfs/w/list) and it would be great if we could expand more on uses and howtos etc.

Alex

[David Champion]

* On 23 Oct 2009, Dustin wrote:
>
> We've got three places for downloads, a few repositories (at least
> two toplevel git repos and a mercurial repo), two places to file bugs,

I agree, there should be consolidation. Using both Google Code and
Github seemed inefficient to me, so I created the Bitbucket repo just so
that people could see what it would look like to use that site alone.

If people doing the work agree categorically that they don't want to use
Bitbucket/mercurial that's fine. I plan to take that repo down after a
little while in either case, because mine shouldn't be the hosting ID.

So it's just a demo, and not a factor as far as worrying about
divergence. It's even part of an effort to organize. :)

--
-D. d...@uchicago.edu NSIT University of Chicago

[Nathan]

On Fri, Oct 23, 2009 at 5:24 PM, Dustin <dsal...@gmail.com> wrote:
>> As for the repositories; the git import (by peaceful) is great,
>> because it contains all the SVN information and history.
>
>   Yeah, that's the (at least) second one that I've seen.  I've done
> some work in mine (and should get bonus points for the umlaut on
> Nöel.) :)

Ouch! C'mon, I'm an ignorant American who only speaks English,
Russian, and Spanish--none of which use the umlauts (aka funny dot
thingies). And I was in a hurry to get the repo into github before it
disappeared! :-)

By the way, is Noel (with the umlaut that I don't know how to type)
male or female? I've always wondered that...

Oh, and I'm fine going with whatever the majority want as far as repo
locations, web sites, etc. As I said before I just made my github
repos to make absolutely sure that we didn't _lose_ what Apple had
published.

~ Nathan

[Jason Richard McNeil]

Indeed.

I'm not certain if Dustin is volunteering to help be a maintainer for
this crazy dream we all seem to share, but it looks like he knows what
he is doing in a number of areas (if anything you might argue he's too
good and ambitious, thus spread thin across many projects).

I'm just a new(ish) C/Objective-C programmer, but I'd recommend we use
Dustin's github repo as the canonical root (even if he goes off the
deep end, we can always fork). I'd prefer to keep the issue tracker in
the same location as the source, and as Google Code has issues with
APSL and CDDL, keeping everything in github seems to keep things
simple and collocated while this project is just getting started.

I personally prefer git, so github makes a lot of sense to me, but if
forced to learn Hg, well, "git-hg" or some variation it is ;)

If nothing else, maybe go with Dustin's repo on github for everything
just for a few weeks, see who is doing the actual work of coding/wiki/
etc., and then those doing the work give the directions.

Lastly (almost), I like the IRC idea. #mac-zfs on freenode.org works
for me.

No matter what, I'm doing what little I can, and so long as well all
do, even if it takes a while we will get there. ;)

-- jasonrm

[Alex Blewitt]

On 24 Oct 2009, at 00:49, Nathan wrote:

> On Fri, Oct 23, 2009 at 5:24 PM, Dustin <dsal...@gmail.com> wrote:
>>> As for the repositories; the git import (by peaceful) is great,
>>> because it contains all the SVN information and history.
>>
>> Yeah, that's the (at least) second one that I've seen. I've done
>> some work in mine (and should get bonus points for the umlaut on
>> Nöel.) :)
>

> By the way, is Noel (with the umlaut that I don't know how to type)
> male or female? I've always wondered that...

Last I heard, she was female. But we've not heard from her since the
2nd Sept, so no-one knows what's happened to her ...

> Oh, and I'm fine going with whatever the majority want as far as repo
> locations, web sites, etc. As I said before I just made my github
> repos to make absolutely sure that we didn't _lose_ what Apple had
> published.

Yes, I think we've got a few places so far that have backups of the
code; we're probably good from here on in. The next thing is trying to
move it forward ...

Alex

[Harald Hanche-Olsen]

+ Dustin <dsal...@gmail.com>:

> Yeah, that's the (at least) second one that I've seen. I've done
> some work in mine (and should get bonus points for the umlaut on
> Nöel.) :)

For bonus points, you need to also put the umlaut on the correct
letter. Sorry. Better luck next time around.

- Harald

[Dustin]

On Oct 23, 5:19 pm, Harald Hanche-Olsen <han...@math.ntnu.no> wrote:
> + Dustin <dsalli...@gmail.com>:

>
> >    Yeah, that's the (at least) second one that I've seen.  I've done
> > some work in mine (and should get bonus points for the umlaut on
> > Nöel.) :)
>
> For bonus points, you need to also put the umlaut on the correct
> letter. Sorry. Better luck next time around.

Picky...

You really frightened me for a moment, though. I at least did it
right in the repo.

[Dustin]

On Oct 23, 4:35 pm, David Champion <d...@uchicago.edu> wrote:

> I agree, there should be consolidation.  Using both Google Code and
> Github seemed inefficient to me

It's not bad at all. We do the same thing for memcached. Just need
to get the two projects pointing towards one another. I'll try to
make sure this is sane.

Take a look at how I've set up the Source tab on the google code
project: http://code.google.com/p/maczfs/

> So it's just a demo, and not a factor as far as worrying about
> divergence.  It's even part of an effort to organize. :)

I'm not complaining. Just want to make sure we're all clear here.
I thank anyone for effort who's trying to make my life better. :)

[Harald Hanche-Olsen]

+ Dustin <dsal...@gmail.com>:

> Picky...

Comes from having a name that people screw up in a number of ways.

> You really frightened me for a moment, though. I at least did it
> right in the repo.

Indeed you did. Objection witdrawn, mostly.

- Harald