lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 22 Nov 2011 10:57:46 +0800
From:	Tao Ma <tm@....ma>
To:	Theodore Ts'o <tytso@....edu>
CC:	linux-ext4@...r.kernel.org
Subject: Re: Better organizing ext4 development community

Hi Ted,
On 11/21/2011 11:58 PM, Theodore Ts'o wrote:
> There seems to be an increasing number of people interested in ext4 who
> have been contributing to ext4, and so I thought this might be a good
> time to pen a note about how we might be able to organize things a
> little better.
> 
> The weekly conference calls
> ===========================
> 
> We have a weekly conference call at Monday 8am US/Pacific and 11am
> US/Eastern.  The people who participate on this call are primarily from
> the following companies (alphabetically): Google, HP, IBM, Red Hat, and
> Whamcloud.  The attendees are primarily mostly from the US, due to
> history of who has known about the calls, but also due to the time of
> the conference calls.
> 
> Given there are more people who are participating on this call from
> Asia, especially from Tao Bao and other companies, I think it's
> important that we revisit whether that time is best, and to try to
> invite some folks from the other countries to participate.   I know that
> language may be a barrier in some cases, but I think it's important that
> we try to get a wider representation that has a chance to hear what's
> going.
> 
> I'd like to hear what folks from Asia think about this; if we started
> having some conference calls that alternated between being convenient
> for folks based out of Asia time zones and folks based out of US time
> zones, would that be helpful?
We are glad to attend this conference call, but have 2 concerns here:
1. about the time. Are there any guys from Europe attend this concall?
If not, I would recommend 4-5PM PT, which means 7-8PM east time and
aroudn 8am here in Asia. We have the concall at that time when I was in
my previous company. If there are some guys from Europe, I think it
would be a pain for them and then I am OK with the current time.
2. about the access number. Are there any local provider for the concall
service? I don't think the company(or us) can cover the long-distance
call :) and a local access number or a toll free one would be great.
> 
> Getting together for a face to face meeting
> ===========================================
> 
> Again, because of the fact that we quite a few newcomers to the ext4
> development community, it seems that it might be a good idea if we could
> get together so we could know each other better.  I'd like to propose
> that we try doing so either immediately before or immediately after the
> Linux Storage, File System, and MM workshop in San Fracisco, which will
> be taking place during the first week of April next year.  I'm hoping
> that we can get good representation from all of the companies who have
> an interest in ext4 development, and if we start early, we can hopefully
> get people thinking about some kind of discussion topic to propose for
> the LSF workshop (proposing a discussion topic that would be of general
> interest is how you get an invite to the LSF), and so people have ample
> time to work out the logistics --- getting travel approval, getting
> Visa's, etc.
> 
> If you would be interested in attending an ext4 get together next year
> in April, please let me know, so I can start guaging interesting and
> numbers.
Coly and I had attended this year's LSF and it would be really
appreciated if we will get invited next year also.
> 
> Review Bottleneck
> =================
> 
> Currently, patches, especially large patch series which introduce some
> new feature, have become bottlenecked on my time to review them.   It
> would be very helpful if we had more people reviewing patches.  And it
> needs to be substantive reviews, and preferably from people who work at
> companies other than the developer who has submitted the patches.
> 
> So some way that we can get more people reviewing patches would
> certainly be helpful.  There have been some people who have suggested
> different ways that we might do things, from the method used in XFS
> (where no patch gets submitted until it gets an independent review;
> which would be a bit scary since at the moment so little review takes
> place I'm concerned it would hold back development significantly), to
> giving people patchwork accounts and formally delegating work to people
> (it has worked for some subsystems, and utterly failed for others).
> 
> Or we could keep going with the current method, with people
> understanding that if you review other people's patches, it makes it
> more likely I will have time to integrate your patches (and if some
> folks do more review work, I'll take that into account about which
> patches series I'm more likely to review myself for integration).
Fine, we will try to spare some time to review others work if we
consider ourselves qualified.
> 
> 
> What do you think?  This, like all of the other parts of this note, was
> meant to start a discussion.  I've been extraordinarily pleased with
> Ext4 development: with what we've been able to achieve, and the people
> we've managed to attract to use and to work on this project.   With your
> help, we can make things even better!
yeah, actually Tao Bao had began to migrate our production systems to be
based on ext4 earlier this year and we will continue to put more guys in
the ext4 development. And we would be glad to see ext4 be more stable
and feature complete in the near future.

Thanks
Tao
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ