On Sat, Sep 29, 2012 at 02:00:36PM +0800, Robin Lee wrote:
On Sat, Sep 29, 2012 at 1:32 PM, Toshio Kuratomi
On Sat, Sep 29, 2012 at 12:24:40PM +0800, Robin Lee wrote:
> On Sat, Sep 29, 2012 at 12:02 PM, Jason L Tibbitts III <tibbs(a)math.uh.edu
> >>>>> "RL" == Robin Lee
> RL> Hi, all I want to follow the route  to bring up a new
> RL> packager.
> Then why not follow the procedure you referenced? It tells you what
> do, which involves opening a ticket in the appropriate trac instance.
> - J<
> It is just the beginning at this moment. The candidate packager is still
> learning RPM packaging and below level that can be sponsored.
> I just thought that the 'newpackager' is the group for such kind of new
> contributors. People in this group can have access to limited group of
> and cannot own any package. But, after all, the group is not existing.
> So, that means new willing contributors can only co-maintain the package
> sending patches and filing bugs, instead of having direct commit
> the Git repo?
Not at all.
If you are willing to mentor the new packager, then they can be sponsored
into the packager group.
If you are not a sponsor yourself, you open a ticket in fesco's trac
who you'd like to have sponosred and that you will be mentoring them as
comaintain which package with you.
At this moment I don't approve him to be sponsored.
So at this moment, can he only send patches to me to co-maintain the package?
If you're unwilling to mentor him, then that is correct.
Can he have git commit privilege to that single package?
People in the packager group only have commit privileges to the packages
that they own or have been granted the commit acl on. So if he is in
packager and only has commit acls on that single package then that's all
that he'll have access to.