info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Uploading a Blog!!!
3 views
Skip to first unread message
Subhasis Chatterjee
Jul 17, 2016, 12:59:12 PM7/17/16
to PMJ Creations, communi...@lists.mozilla.org, Biraj Karmakar
Dear Jafar,
Since last few days I've been constantly trying to upload my blog on an ongoing event (One_Web) with your help,
But till date, it hasn't been uploaded due to various reasons.
Firstly, the blog didn't meet the Mozilla manifesto, so u wanted me to revise, which I readily did, though at various points
I wasn't very much convinced with your logic.
Secondly, the site was down and hence the blog couldn't be uploaded.
Thirdly, (the latest scenario), u asked me to go through the SOP and take the initiative to upload the "revised & ready" event blog
of my own. Now I've gone through the SOP (just copy-pasting it below for your reference once again) and sorry to say, the process is
very very cumbersome.
Contributor
Any community member who needs to author a post that fits the content policy can become a contributor.
They may request to be so by:
a.. filing a bug on bugz.mozillaindia.org with:
a.. their username on the Mozilla India blog
a.. a draft of the post they have, or at least a detailed description of what they want to write about
Following that any documentation team member shall:
a.. verify that the idea behind the post belongs to Mozilla India blog
a.. approve the request with a comment saying so; or
a.. disapprove the request by pointing out where the post would find a better home
Once approved, any administrator shall:
a.. promote the user to a contributor
The contributor shall then proceed to create a new post on the Mozilla India blog. Once they've finished drafting and formatting the post, they'll need an editor to publish the post. They can either approach a willing editor directly through personal message, or:
a.. file a bug on bugz.mozillaindia.org with:
a.. the link to the post pending review
The editor can make changes directly within the post, or suggest changes on the bug. Once satisfied they shall publish the post.
For convenience or saving time, the finalized draft, if available, can be added to the bug requesting contributor access and an editor can review the post simultaneously while the contributor access is being granted.
Now, if this is the way, somebody has to contribute a blog, will modify/revise and then has to cross so many hardle to upload the same, I believe it is a great test of his patience.
Just imagine, for getting uploaded of his just one blog, how much time and effort he / she has to put in?
Instead, why can't we think of giving access to uploading to a registered contrbutor with admin facilities, so that he/she can submit the blog and the designated EDITOR will finally
publish the same. For all the well-khown portals or vortals, their registered contrbutors, writers or Journalists follow the same process. Why can't we?
Pls give it a thought.
Thanks & regards,
Subhasis Chatterjee
Since last few days I've been constantly trying to upload my blog on an ongoing event (One_Web) with your help,
But till date, it hasn't been uploaded due to various reasons.
Firstly, the blog didn't meet the Mozilla manifesto, so u wanted me to revise, which I readily did, though at various points
I wasn't very much convinced with your logic.
Secondly, the site was down and hence the blog couldn't be uploaded.
Thirdly, (the latest scenario), u asked me to go through the SOP and take the initiative to upload the "revised & ready" event blog
of my own. Now I've gone through the SOP (just copy-pasting it below for your reference once again) and sorry to say, the process is
very very cumbersome.
Contributor
Any community member who needs to author a post that fits the content policy can become a contributor.
They may request to be so by:
a.. filing a bug on bugz.mozillaindia.org with:
a.. their username on the Mozilla India blog
a.. a draft of the post they have, or at least a detailed description of what they want to write about
Following that any documentation team member shall:
a.. verify that the idea behind the post belongs to Mozilla India blog
a.. approve the request with a comment saying so; or
a.. disapprove the request by pointing out where the post would find a better home
Once approved, any administrator shall:
a.. promote the user to a contributor
The contributor shall then proceed to create a new post on the Mozilla India blog. Once they've finished drafting and formatting the post, they'll need an editor to publish the post. They can either approach a willing editor directly through personal message, or:
a.. file a bug on bugz.mozillaindia.org with:
a.. the link to the post pending review
The editor can make changes directly within the post, or suggest changes on the bug. Once satisfied they shall publish the post.
For convenience or saving time, the finalized draft, if available, can be added to the bug requesting contributor access and an editor can review the post simultaneously while the contributor access is being granted.
Now, if this is the way, somebody has to contribute a blog, will modify/revise and then has to cross so many hardle to upload the same, I believe it is a great test of his patience.
Just imagine, for getting uploaded of his just one blog, how much time and effort he / she has to put in?
Instead, why can't we think of giving access to uploading to a registered contrbutor with admin facilities, so that he/she can submit the blog and the designated EDITOR will finally
publish the same. For all the well-khown portals or vortals, their registered contrbutors, writers or Journalists follow the same process. Why can't we?
Pls give it a thought.
Thanks & regards,
Subhasis Chatterjee
Akshay S Dinesh
Jul 17, 2016, 2:25:45 PM7/17/16
to PMJ Creations, Subhasis Chatterjee, community-india, Biraj Karmakar
> Now, if this is the way, somebody has to contribute a blog, will modify/revise and then has to cross so many hardle to upload the same, I believe it is a great test of his patience.
> Just imagine, for getting uploaded of his just one blog, how much time and effort he / she has to put in?
>
> Instead, why can't we think of giving access to uploading to a registered contrbutor with admin facilities, so that he/she can submit the blog and the designated EDITOR will finally
> publish the same. For all the well-khown portals or vortals, their registered contrbutors, writers or Journalists follow the same process. Why can't we?
>
Thanks for your valuable feedback on the SOP draft I made.
> Just imagine, for getting uploaded of his just one blog, how much time and effort he / she has to put in?
>
> Instead, why can't we think of giving access to uploading to a registered contrbutor with admin facilities, so that he/she can submit the blog and the designated EDITOR will finally
> publish the same. For all the well-khown portals or vortals, their registered contrbutors, writers or Journalists follow the same process. Why can't we?
>
Here are the hurdles you mention
1) file a bug on mozilla india bugzilla (which includes having to
create an account) with details about their blog account and the
details about the post they're hoping to get published.
2) getting someone from the documentation team to vouch for the idea
and account.
3) the actual process of drafting post, getting reviewed by an editor,
and publishing.
Of this, the 3rd hurdle, I'm sure everyone agrees, is unavoidable.
Hurdle 1 is about where to document these administrator actions. I
chose bugzilla because it is used by mozilla and think is the right
tool for this job.
Regarding hurdle 2, lthough it says someone from documentation team
has to give a thumbs-up before anyone can be made a contributor, I've
been using the loophole that I myself am a member of the documentation
team (by virtue of appending my name to an etherpad document in the
last task force meetup) to grant contributor access without having to
involve a lot of people.
It has worked in the following cases
* http://bugz.mozillaindia.org/show_bug.cgi?id=34
* http://bugz.mozillaindia.org/show_bug.cgi?id=35
* http://bugz.mozillaindia.org/show_bug.cgi?id=43
And, it has resulted in Shri Subramanyam here not getting contributor access yet
* http://bugz.mozillaindia.org/show_bug.cgi?id=37
With those examples in mind, here are the advantages of documentation
team having to vet someone before they're given contributor access.
1) it eliminates the chance of anyone being disappointed because they
found out their blog post didn't belong to the blog after becoming a
contributor (or even after drafting it)
2) it eliminates the need for an admin to log in to the backend for
every one who decides that they require contributor access. (For this,
we could have a system where anyone who signs up gets contributor
access directly. But remember that the drafts by any contributor
appear in the same view together and it can get cluttered with
unwanted drafts if contributor access is open to public.)
I'm definitely happy to see well thought modifications to this SOP.
Also, we should figure out the ownership of and power distribution on
the blog. Probably in the community consultation and reboot that is to
come in the coming weeks, we'll have found answers to all questions.
Akshay
PS: "Uploading a Blog!!!"? Seriously?
PMJ Creations
Jul 18, 2016, 2:46:26 PM7/18/16
to Akshay S Dinesh, community-india, Subhasis Chatterjee, Biraj Karmakar
Dear Subhasis,
The reason is not about aligning your blog post with our manifesto. It's
about the style of your draft and the words you used. An editor role here
does not just publish the draft. They are responsible for the accuracy of
the statements, tone of the copy, and of course aligning our community
goals and values with the content. I believe an editor sometimes used to
impose his thoughts and the organisation values to any authors and their
write up.
Arkodyuti Saha went through the process recently. Initially, his post had
more than 2000 words, and now it's just below 400. Because there were a lot
of unnecessary information and our users won't find it is an interesting
article, so I asked him to clear all the noises as much he can, and we
removed them and published the short and crisp version of the blog. There
is another blog post about the Rust community efforts which is still being
processed. Luckily we got a technical reviewer, and he made a lot of
improvement in the draft. Whether it's a tweet or a blog post, a single
point of failure will harm our community, and we all are trying to avoid
them.
Thanks for initiating this discussion. Do you have a better way to improve
our communication channels? Do let me know.
Jafar Muhammed
Mozillian <http://mozillians.org/en-US/u/pmjcreations/>
On Sun, Jul 17, 2016 at 11:55 PM, Akshay S Dinesh <asdof...@gmail.com>
wrote:
The reason is not about aligning your blog post with our manifesto. It's
about the style of your draft and the words you used. An editor role here
does not just publish the draft. They are responsible for the accuracy of
the statements, tone of the copy, and of course aligning our community
goals and values with the content. I believe an editor sometimes used to
impose his thoughts and the organisation values to any authors and their
write up.
Arkodyuti Saha went through the process recently. Initially, his post had
more than 2000 words, and now it's just below 400. Because there were a lot
of unnecessary information and our users won't find it is an interesting
article, so I asked him to clear all the noises as much he can, and we
removed them and published the short and crisp version of the blog. There
is another blog post about the Rust community efforts which is still being
processed. Luckily we got a technical reviewer, and he made a lot of
improvement in the draft. Whether it's a tweet or a blog post, a single
point of failure will harm our community, and we all are trying to avoid
them.
Thanks for initiating this discussion. Do you have a better way to improve
our communication channels? Do let me know.
Jafar Muhammed
Mozillian <http://mozillians.org/en-US/u/pmjcreations/>
On Sun, Jul 17, 2016 at 11:55 PM, Akshay S Dinesh <asdof...@gmail.com>
wrote:
Subhasis Chatterjee
Jul 18, 2016, 3:01:15 PM7/18/16
to PMJ Creations, community-india, Biraj Karmakar, Akshay S Dinesh
Dear Jafar,
I completely respect your views and Mozilla communication guidelines.
Since, I'm a senior pro and content is my area of expertise, so I know it
is our primary duty to be adhered by the guidelines set by Mozilla.
That is why, I modified my blog the way u wanted without a least little
discomfort. Now that the blog is ready for publish (that's what u told me),
u had asked me to follow the SOP and get it published. Now this is my point
of DISCOMFORT. I want to categorically mention that this SOP is very
cumbersome and following the process will take another few days' time
unnecessarily which can eventually ruin the interest level of a blogger.
So, why can't we shorten the process and publish it as soon as the draft is
"ready to publish"?
Hope u understand my concern, Jafar. Let's work on a process to minimize
the in between time.
Thanks & Regards,
Subhasis Chatterjee
On Tue, Jul 19, 2016 at 12:15 AM, PMJ Creations <pmjcre...@gmail.com>
wrote:
I completely respect your views and Mozilla communication guidelines.
Since, I'm a senior pro and content is my area of expertise, so I know it
is our primary duty to be adhered by the guidelines set by Mozilla.
That is why, I modified my blog the way u wanted without a least little
discomfort. Now that the blog is ready for publish (that's what u told me),
u had asked me to follow the SOP and get it published. Now this is my point
of DISCOMFORT. I want to categorically mention that this SOP is very
cumbersome and following the process will take another few days' time
unnecessarily which can eventually ruin the interest level of a blogger.
So, why can't we shorten the process and publish it as soon as the draft is
"ready to publish"?
Hope u understand my concern, Jafar. Let's work on a process to minimize
the in between time.
Thanks & Regards,
Subhasis Chatterjee
On Tue, Jul 19, 2016 at 12:15 AM, PMJ Creations <pmjcre...@gmail.com>
wrote:
PMJ Creations
Jul 19, 2016, 7:35:10 AM7/19/16
to Subhasis Chatterjee, community-india, Biraj Karmakar, Akshay S Dinesh
Dear Subhasis,
Let me help you to understand. As Akshay said, we can't give the
Contributor access by default to every signup due to a valid reason.
Since you have already signed up to our blogging platform, the only thing
blocking you is to get the Contributor access which you can gain quickly by
submitting a new bug. And I do listen to your difficulties, but I can
promise you, this Bugzilla process will not take days as you worrying. If
you can check the bugs Akshay shared above; you will come to know all of
them resolved within an hour or very less than that. And it's just a single
time process, once we are done, we won't repeat this.
Finally, if you have any good solution to make this process ease, please
share that. So we can make it more enjoyable.
I am happy to hear your thoughts.
Let me help you to understand. As Akshay said, we can't give the
Contributor access by default to every signup due to a valid reason.
Since you have already signed up to our blogging platform, the only thing
blocking you is to get the Contributor access which you can gain quickly by
submitting a new bug. And I do listen to your difficulties, but I can
promise you, this Bugzilla process will not take days as you worrying. If
you can check the bugs Akshay shared above; you will come to know all of
them resolved within an hour or very less than that. And it's just a single
time process, once we are done, we won't repeat this.
Finally, if you have any good solution to make this process ease, please
share that. So we can make it more enjoyable.
I am happy to hear your thoughts.
Subhasis Chatterjee
Jul 19, 2016, 10:22:22 AM7/19/16
to PMJ Creations, community-india, Biraj Karmakar, Akshay S Dinesh
As desired, I've created a bug to get contributor access.
Subhasis C
Subhasis C
----- Original Message -----
From: PMJ Creations
To: Subhasis Chatterjee
Cc: Akshay S Dinesh ; Biraj Karmakar ; community-india
Sent: Tuesday, July 19, 2016 5:04 PM
Subject: Re: [Mozilla India] Uploading a Blog!!!
Dear Subhasis,
Let me help you to understand. As Akshay said, we can't give the Contributor access by default to every signup due to a valid reason.
Since you have already signed up to our blogging platform, the only thing blocking you is to get the Contributor access which you can gain quickly by submitting a new bug. And I do listen to your difficulties, but I can promise you, this Bugzilla process will not take days as you worrying. If you can check the bugs Akshay shared above; you will come to know all of them resolved within an hour or very less than that. And it's just a single time process, once we are done, we won't repeat this.
Finally, if you have any good solution to make this process ease, please share that. So we can make it more enjoyable.
I am happy to hear your thoughts.
Jafar Muhammed
Mozillian
From: PMJ Creations
To: Subhasis Chatterjee
Cc: Akshay S Dinesh ; Biraj Karmakar ; community-india
Sent: Tuesday, July 19, 2016 5:04 PM
Subject: Re: [Mozilla India] Uploading a Blog!!!
Dear Subhasis,
Let me help you to understand. As Akshay said, we can't give the Contributor access by default to every signup due to a valid reason.
Since you have already signed up to our blogging platform, the only thing blocking you is to get the Contributor access which you can gain quickly by submitting a new bug. And I do listen to your difficulties, but I can promise you, this Bugzilla process will not take days as you worrying. If you can check the bugs Akshay shared above; you will come to know all of them resolved within an hour or very less than that. And it's just a single time process, once we are done, we won't repeat this.
Finally, if you have any good solution to make this process ease, please share that. So we can make it more enjoyable.
I am happy to hear your thoughts.
Jafar Muhammed
Mozillian
On Tue, Jul 19, 2016 at 12:31 AM, Subhasis Chatterjee <connec...@gmail.com> wrote:
Dear Jafar,
I completely respect your views and Mozilla communication guidelines.
Since, I'm a senior pro and content is my area of expertise, so I know it is our primary duty to be adhered by the guidelines set by Mozilla.
That is why, I modified my blog the way u wanted without a least little discomfort. Now that the blog is ready for publish (that's what u told me), u had asked me to follow the SOP and get it published. Now this is my point of DISCOMFORT. I want to categorically mention that this SOP is very cumbersome and following the process will take another few days' time unnecessarily which can eventually ruin the interest level of a blogger. So, why can't we shorten the process and publish it as soon as the draft is "ready to publish"?
Hope u understand my concern, Jafar. Let's work on a process to minimize the in between time.
Thanks & Regards,
Subhasis Chatterjee
On Tue, Jul 19, 2016 at 12:15 AM, PMJ Creations <pmjcre...@gmail.com> wrote:
Dear Subhasis,
The reason is not about aligning your blog post with our manifesto. It's about the style of your draft and the words you used. An editor role here does not just publish the draft. They are responsible for the accuracy of the statements, tone of the copy, and of course aligning our community goals and values with the content. I believe an editor sometimes used to impose his thoughts and the organisation values to any authors and their write up.
Arkodyuti Saha went through the process recently. Initially, his post had more than 2000 words, and now it's just below 400. Because there were a lot of unnecessary information and our users won't find it is an interesting article, so I asked him to clear all the noises as much he can, and we removed them and published the short and crisp version of the blog. There is another blog post about the Rust community efforts which is still being processed. Luckily we got a technical reviewer, and he made a lot of improvement in the draft. Whether it's a tweet or a blog post, a single point of failure will harm our community, and we all are trying to avoid them.
Thanks for initiating this discussion. Do you have a better way to improve our communication channels? Do let me know.
Jafar Muhammed
Mozillian
Dear Jafar,
I completely respect your views and Mozilla communication guidelines.
Since, I'm a senior pro and content is my area of expertise, so I know it is our primary duty to be adhered by the guidelines set by Mozilla.
That is why, I modified my blog the way u wanted without a least little discomfort. Now that the blog is ready for publish (that's what u told me), u had asked me to follow the SOP and get it published. Now this is my point of DISCOMFORT. I want to categorically mention that this SOP is very cumbersome and following the process will take another few days' time unnecessarily which can eventually ruin the interest level of a blogger. So, why can't we shorten the process and publish it as soon as the draft is "ready to publish"?
Hope u understand my concern, Jafar. Let's work on a process to minimize the in between time.
Thanks & Regards,
Subhasis Chatterjee
On Tue, Jul 19, 2016 at 12:15 AM, PMJ Creations <pmjcre...@gmail.com> wrote:
Dear Subhasis,
The reason is not about aligning your blog post with our manifesto. It's about the style of your draft and the words you used. An editor role here does not just publish the draft. They are responsible for the accuracy of the statements, tone of the copy, and of course aligning our community goals and values with the content. I believe an editor sometimes used to impose his thoughts and the organisation values to any authors and their write up.
Arkodyuti Saha went through the process recently. Initially, his post had more than 2000 words, and now it's just below 400. Because there were a lot of unnecessary information and our users won't find it is an interesting article, so I asked him to clear all the noises as much he can, and we removed them and published the short and crisp version of the blog. There is another blog post about the Rust community efforts which is still being processed. Luckily we got a technical reviewer, and he made a lot of improvement in the draft. Whether it's a tweet or a blog post, a single point of failure will harm our community, and we all are trying to avoid them.
Thanks for initiating this discussion. Do you have a better way to improve our communication channels? Do let me know.
Jafar Muhammed
Mozillian
PMJ Creations
Jul 19, 2016, 11:58:01 PM7/19/16
to Subhasis Chatterjee, community-india, Biraj Karmakar, Akshay S Dinesh
The blog post is live now. However, Subhasis, let's not make this
discussion and interests ended here. Lets keep working on the improvisation
of the process and try to generate as much quality content as we can.
Jafar Muhammed
Typed with thumbs while on the go. Erroneous words are a feature, not a
typo.
On 19-Jul-2016 7:52 PM, "Subhasis Chatterjee" <connec...@gmail.com>
wrote:
> As desired, I've created a bug to get contributor access.
>
> Subhasis C
>
> ----- Original Message -----
> *From:* PMJ Creations <pmjcre...@gmail.com>
> *To:* Subhasis Chatterjee <connec...@gmail.com>
> *Cc:* Akshay S Dinesh <asdof...@gmail.com> ; Biraj Karmakar
> <brn...@gmail.com> ; community-india <communi...@lists.mozilla.org>
> *Sent:* Tuesday, July 19, 2016 5:04 PM
> *Subject:* Re: [Mozilla India] Uploading a Blog!!!
>>> Mozillian <http://mozillians.org/en-US/u/pmjcreations/>
discussion and interests ended here. Lets keep working on the improvisation
of the process and try to generate as much quality content as we can.
Jafar Muhammed
Typed with thumbs while on the go. Erroneous words are a feature, not a
typo.
On 19-Jul-2016 7:52 PM, "Subhasis Chatterjee" <connec...@gmail.com>
wrote:
> As desired, I've created a bug to get contributor access.
>
> Subhasis C
>
> ----- Original Message -----
> *To:* Subhasis Chatterjee <connec...@gmail.com>
> *Cc:* Akshay S Dinesh <asdof...@gmail.com> ; Biraj Karmakar
> <brn...@gmail.com> ; community-india <communi...@lists.mozilla.org>
> *Sent:* Tuesday, July 19, 2016 5:04 PM
> *Subject:* Re: [Mozilla India] Uploading a Blog!!!
>
> Dear Subhasis,
>
> Let me help you to understand. As Akshay said, we can't give the
> Contributor access by default to every signup due to a valid reason.
> Since you have already signed up to our blogging platform, the only thing
> blocking you is to get the Contributor access which you can gain quickly by
> submitting a new bug. And I do listen to your difficulties, but I can
> promise you, this Bugzilla process will not take days as you worrying. If
> you can check the bugs Akshay shared above; you will come to know all of
> them resolved within an hour or very less than that. And it's just a single
> time process, once we are done, we won't repeat this.
>
> Finally, if you have any good solution to make this process ease, please
> share that. So we can make it more enjoyable.
>
> I am happy to hear your thoughts.
>
>
> Jafar Muhammed
> Mozillian <http://mozillians.org/en-US/u/pmjcreations/>
> Dear Subhasis,
>
> Let me help you to understand. As Akshay said, we can't give the
> Contributor access by default to every signup due to a valid reason.
> Since you have already signed up to our blogging platform, the only thing
> blocking you is to get the Contributor access which you can gain quickly by
> submitting a new bug. And I do listen to your difficulties, but I can
> promise you, this Bugzilla process will not take days as you worrying. If
> you can check the bugs Akshay shared above; you will come to know all of
> them resolved within an hour or very less than that. And it's just a single
> time process, once we are done, we won't repeat this.
>
> Finally, if you have any good solution to make this process ease, please
> share that. So we can make it more enjoyable.
>
> I am happy to hear your thoughts.
>
>
> Jafar Muhammed
Subhasis Chatterjee
Jul 20, 2016, 12:55:15 AM7/20/16
to PMJ Creations, community-india, Biraj Karmakar, Akshay S Dinesh
Thanks so much Jafar for making it live.
Regards,
Regards,
Subhasis C
----- Original Message -----
----- Original Message -----
From: PMJ Creations
To: Subhasis Chatterjee
To: Subhasis Chatterjee
Cc: community-india ; Akshay S Dinesh ; Biraj Karmakar
Sent: Wednesday, July 20, 2016 9:27 AM
Subject: Re: [Mozilla India] Uploading a Blog!!!
The blog post is live now. However, Subhasis, let's not make this discussion and interests ended here. Lets keep working on the improvisation of the process and try to generate as much quality content as we can.
Jafar Muhammed
Typed with thumbs while on the go. Erroneous words are a feature, not a typo.
On 19-Jul-2016 7:52 PM, "Subhasis Chatterjee" <connec...@gmail.com> wrote:
As desired, I've created a bug to get contributor access.
Subhasis C
----- Original Message -----
Sent: Wednesday, July 20, 2016 9:27 AM
Subject: Re: [Mozilla India] Uploading a Blog!!!
The blog post is live now. However, Subhasis, let's not make this discussion and interests ended here. Lets keep working on the improvisation of the process and try to generate as much quality content as we can.
Jafar Muhammed
Typed with thumbs while on the go. Erroneous words are a feature, not a typo.
On 19-Jul-2016 7:52 PM, "Subhasis Chatterjee" <connec...@gmail.com> wrote:
As desired, I've created a bug to get contributor access.
Subhasis C
----- Original Message -----
From: PMJ Creations
To: Subhasis Chatterjee
Cc: Akshay S Dinesh ; Biraj Karmakar ; community-india
To: Subhasis Chatterjee
Cc: Akshay S Dinesh ; Biraj Karmakar ; community-india
Sent: Tuesday, July 19, 2016 5:04 PM
Subject: Re: [Mozilla India] Uploading a Blog!!!
Dear Subhasis,
Let me help you to understand. As Akshay said, we can't give the Contributor access by default to every signup due to a valid reason.
Since you have already signed up to our blogging platform, the only thing blocking you is to get the Contributor access which you can gain quickly by submitting a new bug. And I do listen to your difficulties, but I can promise you, this Bugzilla process will not take days as you worrying. If you can check the bugs Akshay shared above; you will come to know all of them resolved within an hour or very less than that. And it's just a single time process, once we are done, we won't repeat this.
Finally, if you have any good solution to make this process ease, please share that. So we can make it more enjoyable.
I am happy to hear your thoughts.
Jafar Muhammed
Mozillian
Subject: Re: [Mozilla India] Uploading a Blog!!!
Dear Subhasis,
Let me help you to understand. As Akshay said, we can't give the Contributor access by default to every signup due to a valid reason.
Since you have already signed up to our blogging platform, the only thing blocking you is to get the Contributor access which you can gain quickly by submitting a new bug. And I do listen to your difficulties, but I can promise you, this Bugzilla process will not take days as you worrying. If you can check the bugs Akshay shared above; you will come to know all of them resolved within an hour or very less than that. And it's just a single time process, once we are done, we won't repeat this.
Finally, if you have any good solution to make this process ease, please share that. So we can make it more enjoyable.
I am happy to hear your thoughts.
Jafar Muhammed
Mozillian
On Tue, Jul 19, 2016 at 12:31 AM, Subhasis Chatterjee <connec...@gmail.com> wrote:
Dear Jafar,
I completely respect your views and Mozilla communication guidelines.
Since, I'm a senior pro and content is my area of expertise, so I know it is our primary duty to be adhered by the guidelines set by Mozilla.
That is why, I modified my blog the way u wanted without a least little discomfort. Now that the blog is ready for publish (that's what u told me), u had asked me to follow the SOP and get it published. Now this is my point of DISCOMFORT. I want to categorically mention that this SOP is very cumbersome and following the process will take another few days' time unnecessarily which can eventually ruin the interest level of a blogger. So, why can't we shorten the process and publish it as soon as the draft is "ready to publish"?
Hope u understand my concern, Jafar. Let's work on a process to minimize the in between time.
Thanks & Regards,
Subhasis Chatterjee
On Tue, Jul 19, 2016 at 12:15 AM, PMJ Creations <pmjcre...@gmail.com> wrote:
Dear Subhasis,
The reason is not about aligning your blog post with our manifesto. It's about the style of your draft and the words you used. An editor role here does not just publish the draft. They are responsible for the accuracy of the statements, tone of the copy, and of course aligning our community goals and values with the content. I believe an editor sometimes used to impose his thoughts and the organisation values to any authors and their write up.
Arkodyuti Saha went through the process recently. Initially, his post had more than 2000 words, and now it's just below 400. Because there were a lot of unnecessary information and our users won't find it is an interesting article, so I asked him to clear all the noises as much he can, and we removed them and published the short and crisp version of the blog. There is another blog post about the Rust community efforts which is still being processed. Luckily we got a technical reviewer, and he made a lot of improvement in the draft. Whether it's a tweet or a blog post, a single point of failure will harm our community, and we all are trying to avoid them.
Thanks for initiating this discussion. Do you have a better way to improve our communication channels? Do let me know.
Jafar Muhammed
Mozillian
Dear Jafar,
I completely respect your views and Mozilla communication guidelines.
Since, I'm a senior pro and content is my area of expertise, so I know it is our primary duty to be adhered by the guidelines set by Mozilla.
That is why, I modified my blog the way u wanted without a least little discomfort. Now that the blog is ready for publish (that's what u told me), u had asked me to follow the SOP and get it published. Now this is my point of DISCOMFORT. I want to categorically mention that this SOP is very cumbersome and following the process will take another few days' time unnecessarily which can eventually ruin the interest level of a blogger. So, why can't we shorten the process and publish it as soon as the draft is "ready to publish"?
Hope u understand my concern, Jafar. Let's work on a process to minimize the in between time.
Thanks & Regards,
Subhasis Chatterjee
On Tue, Jul 19, 2016 at 12:15 AM, PMJ Creations <pmjcre...@gmail.com> wrote:
Dear Subhasis,
The reason is not about aligning your blog post with our manifesto. It's about the style of your draft and the words you used. An editor role here does not just publish the draft. They are responsible for the accuracy of the statements, tone of the copy, and of course aligning our community goals and values with the content. I believe an editor sometimes used to impose his thoughts and the organisation values to any authors and their write up.
Arkodyuti Saha went through the process recently. Initially, his post had more than 2000 words, and now it's just below 400. Because there were a lot of unnecessary information and our users won't find it is an interesting article, so I asked him to clear all the noises as much he can, and we removed them and published the short and crisp version of the blog. There is another blog post about the Rust community efforts which is still being processed. Luckily we got a technical reviewer, and he made a lot of improvement in the draft. Whether it's a tweet or a blog post, a single point of failure will harm our community, and we all are trying to avoid them.
Thanks for initiating this discussion. Do you have a better way to improve our communication channels? Do let me know.
Jafar Muhammed
Mozillian
0 new messages