User Agent: Mozilla/5.0 (Windows NT 6.1; rv:6.0) Gecko/20100101 Firefox/6.0 Build ID: 20110811165603 Steps to reproduce: my email address is email@example.com,i want to have access to the bn-IN localization branch
Summary: Commit Access Level 3 for Swarnava Sengupta → Commit Access Level 2 for Swarnava Sengupta
Summary: Commit Access Level 2 for Swarnava Sengupta → Commit Access Level 1a for Swarnava Sengupta
Is this the right place for Swarnava to request commit access to the bn-IN branch, or should this go into the Repository Account Requests component?
Component: Localization Server → Repository Account Requests
Assignee: reed → mozillamarcia.knous
QA Contact: l10n-server → repo-acct-req
Who is vouching for this account?
Mail Sent to Erica McClure
(In reply to Runa Bhattacharjee from comment #3) > Who is vouching for this account? You'd be the one to vouch here, or Sankarshan. Generally, the existing localizers vouch for access for new contributors. Technically, I back that up afterwards, so that our IT guys don't need to dig up names of who's doing what and can vouch and all that.
Summary: Commit Access Level 1a for Swarnava Sengupta → l10n Commit Access Level 1a for Swarnava Sengupta [bn-IN]
(In reply to Axel Hecht [:Pike] from comment #5) > > You'd be the one to vouch here, or Sankarshan. Generally, the existing > localizers vouch for access for new contributors. I am sorry, but I am not and I can also safely say the same for Sankarshan. It was made adequately clear to Swarnava that we would like him to start off as a translator, be reviewed and understand how the team works with the content. At this point he is a probie and I was under the impression that this matter was already settled to be taken up in the future. Our team (http://ankur.org.in/) shall personally not take any responsibility if there is any loss of content in the current bn_IN live trees.
That's totally fine. We're requiring vouchers for all our repos for the very reason that the existing contributors are comfortable with the new committer landing patches on their own. That understanding is usually built up by providing patches before getting write access, so I suggest that Swarnava does that, and I guess that's already under way. I'll resolve this bug as incomplete for now. Feel free to reopen once the team is comfortable with Swarnava's contributions to go directly to version control. We'll be able to pick things up smoothely from what we have so far then.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
Thank you. We'll mentor him in the coming weeks/months and return when he is ready.
I have received Swarnava's Committer's Agreement.
this request is just to localize Mozilla webdev sites like SUMO, AMO, etc. Do the same rules about requiring patches before granting commit access still apply here? Can the account request be re-opened? As I understand it, an SVN account is required to begin translating, per https://wiki.mozilla.org/SVN#SVN_account_for_localizers
To clarify, this request is about access to the hg repositories. Re SVN, Swarnava can contribute on verbatim without svn access, and attach patches with his work for hg.
You need to log in before you can comment on or make changes to this bug.