Dear Chris:

Yes, I have cced [email protected] on personnel matters.
Thanks for the guidance.

Best regards,
Jia

On Fri, Jul 8, 2016 at 8:56 AM, Mattmann, Chris A (3980) <
[email protected]> wrote:

> Hi Jia,
>
> When you contact the students, please CC [email protected]
> and get in the habit of doing so related to personnel matters. We need
> transparency in the communications related to the project so this is a
> good opportunity to do so. Also that lets others chime in and help/and
> be part of the conversation.
>
> As for the web page, I am assuming you are talking about:
>
> http://cmda.incubator.apache.org/
>
> Which currently doesn’t have a web page associated with this. We can
> easily deal with that - someone from Apache CMDA can easily file an
> INFRA ticket here:
>
> http://issues.apache.org/jira/browse/INFRA
>
> And request that a web presence space be set up. Our options are:
>
> 1. custom HTML website generated by our own process and simply updated
> in SVN.
> 2. Apache Content Management System (CMS)
>   http://www.apache.org/dev/cmsref.html
>
> We need to decide on #1 or #2 before contacting INFRA.
>
> HTH!
>
> Cheers,
> Chris
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Chief Architect
> Instrument Software and Science Data Systems Section (398)
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 168-519, Mailstop: 168-527
> Email: [email protected]
> WWW:  http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Director, Information Retrieval and Data Science Group (IRDS)
> Adjunct Associate Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> WWW: http://irds.usc.edu/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
>
>
>
>
>
>
>
> On 7/8/16, 8:50 AM, "Jia Zhang" <[email protected]> wrote:
>
> >Dear Greg:
> >
> >Oh, good.
> >
> >That being said, I will notify the previous students that they could
> choose
> >to request to be moved to "emeritus" status or removed from the PMC, or
> >they can choose to stay within the community and continue to contribute.
> >
> >Meanwhile, who we should contact to update the homepage of the CMDA
> >project? We plan to update the homepage to further explain the project
> >goals, strategy etc to call for more contribution in the community.
> >
> >Thanks a lot.
> >
> >Best regards,
> >Jia
> >
> >On Fri, Jul 8, 2016 at 2:41 AM, Greg Reddin <[email protected]> wrote:
> >
> >> Also, people are almost never removed from a project. Merit never
> >> expires even if the person walks away from the project. A person who
> >> is no longer involved can ask to be moved to "emeritus" status or
> >> removed from the PMC. But it would be at his/her request not a move of
> >> the community.
> >>
> >> Greg
> >>
> >> On Thu, Jul 7, 2016 at 5:54 PM, Mattmann, Chris A (3980)
> >> <[email protected]> wrote:
> >> > Hi Jia,
> >> >
> >> > Thanks. Please check out:
> >> >
> >> > http://www.apache.org/foundation/voting.html
> >> >
> >> >
> >> > Also please note discussions of specific personnel should be held
> >> > on the [email protected] list. One of the only (few)
> >> > things that are private the the ASF.
> >> >
> >> > Please start with a [DISCUSS] <Person Name> as an Apache CMDA
> >> PPMC/committer
> >> >
> >> > Thread, followed by a [VOTE] <Person Name> as an Apache CMDA
> >> PPMC/committer
> >> > thread say 48-72 hours after if there are no objections.
> >> >
> >> > We also can’t bulk remove or add people, we must VOTE them in one
> >> > by one, and describe why/based on technical merit, prior background
> >> > experience, goodness for the community, etc.
> >> >
> >> > Again all of this should be on [email protected].
> >> >
> >> > Cheers,
> >> > Chris
> >> >
> >> >
> >> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >> > Chris Mattmann, Ph.D.
> >> > Chief Architect
> >> > Instrument Software and Science Data Systems Section (398)
> >> > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> >> > Office: 168-519, Mailstop: 168-527
> >> > Email: [email protected]
> >> > WWW:  http://sunset.usc.edu/~mattmann/
> >> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >> > Director, Information Retrieval and Data Science Group (IRDS)
> >> > Adjunct Associate Professor, Computer Science Department
> >> > University of Southern California, Los Angeles, CA 90089 USA
> >> > WWW: http://irds.usc.edu/
> >> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > On 7/7/16, 3:39 PM, "Jia Zhang" <[email protected]> wrote:
> >> >
> >> >>Dear Chris, Greg, and other Mentors:
> >> >>
> >> >>The CMDA community had in-depth discussions today on Greg's
> instructions
> >> on
> >> >>how to become a qualified Apache project. For each item specified by
> >> Greg,
> >> >>we have examined our current workflow and discussed how to adjust
> >> >>accordingly.
> >> >>
> >> >>First thing we would like to do is to organize Apache CMDA
> repository, so
> >> >>that code can be checked into Apache git directly from committers.
> >> >>
> >> >>Would you please help let the following people become committer for
> >> Apache
> >> >>CMDA? Please list them as committers for the project.
> >> >>-QiHaoBao (Qihao Bao)
> >> >>-holysoul (Runyu Shi)
> >> >>
> >> >>Meanwhile, please remove the following committers as they are not
> part of
> >> >>the community any longer.
> >> >>-Wei Wang
> >> >>-Chris Lee
> >> >>-Xing Wei
> >> >>
> >> >>Thanks a lot.
> >> >>
> >> >>Best regards,
> >> >>Jia
> >> >>
> >> >>
> >> >>
> >> >>Second, code is not developed in Apache repositories. Instead it is
> >> >>imported in bulk. For CMDA to be a community-driven project code must
> >> >>be committed directly to the Apache repo first. If some folks need to
> >> >>maintain a fork for their own uses elsewhere, including for student
> >> >>projects, that's fine. But individual commits, not bulk commits need
> >> >>to be taking place in Apache repos, not external ones.
> >> >>
> >> >>Third, decisions are not made by the community. They appear to be made
> >> >>by a few people separate from the dev list and presented here after
> >> >>the fact. We see meeting minutes where things have been decided and
> >> >>assignments made. If I want to contribute to the Docker container, how
> >> >>can I do that? If I want to contribute to improving the HTML front
> >> >>ends how would I go about that? How can someone from the outside of
> >> >>your core group help decide what the next step will be and contribute
> >> >>code? That's the essence of the Apache Way.
> >> >>
> >> >>Now, here are some specific things I need to see before I can say the
> >> >>project is making progress in the right direction.
> >> >>
> >> >>1. Code from school projects should be submitted to Apache by the
> >> >>author and committed to the Apache repo by a CMDA committer. It can be
> >> >>submitted through a Jira attachment, GitHub pull request, etc.
> >> >>
> >> >>2. Discussion regarding school projects should take place on the CMDA
> dev
> >> >>list.
> >> >>
> >> >>3. We must see commits of code to the Apache CMDA repository. These
> >> >>are not imports of large blocks of code worked on for a long time, but
> >> >>individual changes submitted one at a time directly to the Apache
> >> >>project. The Apache repo must be the primary source code repository.
> >> >>
> >> >>4. Make decisions regarding code and project direction on the CMDA dev
> >> >>list. Offlist face-to-face meetings are ok, but no decisions can be
> >> >>made, only recommendations. If someone on list offers an alternative
> >> >>solution to any of those recommendations it must receive equal weight
> >> >>and the community decides collectively how to proceed.
> >> >>
> >> >>Discussions regarding project direction, features, releases, who's
> >> >>working on what, etc. must take place on the CMDA dev list.
> >> >>
> >> >>Finally, please understand that if the project is not compatible with
> >> >>the Apache style of development, it's not a failure. It would not be a
> >> >>bad mark on your "resume'." It would simply mean that the project
> >> >>relies on some tenets of development that are not driven by the
> >> >>community. Perhaps it is better for this project to be presented to
> >> >>the community after work is done, as opposed to allowing the community
> >> >>broad input as to its direction. If so that's fine. But if you want to
> >> >>be at Apache that broad input from the community is an absolute
> >> >>requirement.
> >> >>
> >> >>Please let me know if any clarification of these points is needed.
> >> >>
> >> >>Thanks,
> >> >>Greg
> >> >>Jia Zhang
> >> >>
> >> >>Dear Greg, Thanks a lot for your detailed instructions on Apache
> >> >>requirements...
> >> >>Jul 6 (1 day ago)
> >> >>Mattmann, Chris A (3980) via
> >> >><https://support.google.com/mail/answer/1311182?hl=en>
> >> >>cmda.incubator.apache.org
> >> >>Jul 6 (1 day ago)
> >> >>to dev
> >> >>This is great advice I recommend folks read it carefully.
> >> >>
> >> >>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >> >>Chris Mattmann, Ph.D.
> >> >>Chief Architect
> >> >>Instrument Software and Science Data Systems Section (398)
> >> >>NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> >> >>Office: 168-519, Mailstop: 168-527
> >> >>Email: [email protected]
> >> >>WWW:  http://sunset.usc.edu/~mattmann/
> >> >>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >> >>Director, Information Retrieval and Data Science Group (IRDS)
> >> >>Adjunct Associate Professor, Computer Science Department
> >> >>University of Southern California, Los Angeles, CA 90089 USA
> >> >>WWW: http://irds.usc.edu/
> >> >>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >> >>Lee, Seungwon (398K)
> >> >>
> >> >>Hi, This email describes what Apache way of development should be, and
> >> now
> >> >>I ...
> >> >>Jul 6 (1 day ago)
> >> >>Jia Zhang <[email protected]>
> >> >>Jul 6 (1 day ago)
> >> >>to Seungwon, Lei, Chengxing, Benyang
> >> >>Sounds good. Let's discuss tomorrow.
> >> >>
> >> >>Best regards,
> >> >>Jia
> >> >>Click here to Reply, Reply to all, or Forward
> >> >>Using 42.05 GB
> >> >>Manage <https://accounts.google.com/b/0/ManageStorage?hl=en>
> >> >>Program Policies
> >> >><https://www.gmail.com/intl/en/mail/help/program_policies.html>
> >> >>Powered by
> >> >>Google
> >> >><https://www.google.com/>
> >> >>Last account activity: 0 minutes ago
> >> >>Details
> >> >>People (7)
> >> >>Mattmann, Chris A (3980)
> >> >>
> >> >>Add to circles
> >> >>Show details
> >> >>Compose:
> >> >>Ask to grant Qihao Bao access to Apache repository
> >> >>[image: Minimize][image: Pop-out][image: Close]
> >> >>[email protected]
> >> >>we would like to do is to redirect all code movement to Apache git.
> >> >>
> >> >>Best regards,
> >> >>Jia
> >>
>

Reply via email to