Hi all,
I am proposing to migrate the event guidelines into a Google Doc to provide a single place to point people (with authenticated protection and commenting) and also provide an easier interface for commenting and suggesting changes.
Currently, the guidelines live in this Etherpad:
https://etherpad.persephone.cloud/p/FedoraEventGuidelines
I was reviewing Dyuti's CommBlog draft for the event guidelines post today and realized it would be helpful to point people to one place to read the guidelines. When I was reviewing the original Etherpad, it was difficult to follow between actual content and comments. I think this is a problem others who review the event guidelines will also face, and decrease the chances of receiving meaningful feedback.
Even though Google Docs isn't open source, the benefits it provides for us to collect meaningful feedback, assist our outreach effort, and more effectively meet our goals seems worth it.
I can migrate the content before the end of Friday if helpful. I think it will expedite the speed we can get the Community Blog article published too.
Please let me know your thoughts on migrating the event guidelines into a publicly-visible Google Doc. Otherwise, I will do this before the end of day Friday to help keep momentum with the CommBlog article.
Thanks!
On Thu, Jul 19, 2018 at 11:47 PM, Justin W. Flory jflory7@gmail.com wrote:
Hi all,
I am proposing to migrate the event guidelines into a Google Doc to provide a single place to point people (with authenticated protection and commenting) and also provide an easier interface for commenting and suggesting changes.
+1 to migrating to something that makes it easier to see comments vs. the document.
Another idea would be to code it in asciidoc and submit it as a PR to it's final resting place. This way we have somethign to refer to when we submit it for various approvals and you can make line-by-line comments.
Having a more readable draft would help me with getting Flock as in compliance as it can be.
regards,
bex
Currently, the guidelines live in this Etherpad:
https://etherpad.persephone.cloud/p/FedoraEventGuidelinesI was reviewing Dyuti's CommBlog draft for the event guidelines post today and realized it would be helpful to point people to one place to read the guidelines. When I was reviewing the original Etherpad, it was difficult to follow between actual content and comments. I think this is a problem others who review the event guidelines will also face, and decrease the chances of receiving meaningful feedback.
Even though Google Docs isn't open source, the benefits it provides for us to collect meaningful feedback, assist our outreach effort, and more effectively meet our goals seems worth it.
I can migrate the content before the end of Friday if helpful. I think it will expedite the speed we can get the Community Blog article published too.
Please let me know your thoughts on migrating the event guidelines into a publicly-visible Google Doc. Otherwise, I will do this before the end of day Friday to help keep momentum with the CommBlog article.
Thanks!
-- Cheers, Justin W. Flory jflory7@gmail.com
Fedora Diversity & Inclusion Team mailing list -- diversity@lists.fedoraproject.org To unsubscribe send an email to diversity-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/diversity@ lists.fedoraproject.org/message/V5ENOOMGGTDDWORQZWQEFBVFMKI26GZJ/
On 07/24/2018 06:59 AM, Brian (bex) Exelbierd wrote:
On Thu, Jul 19, 2018 at 11:47 PM, Justin W. Flory <jflory7@gmail.com mailto:jflory7@gmail.com> wrote:
Hi all, I am proposing to migrate the event guidelines into a Google Doc to provide a single place to point people (with authenticated protection and commenting) and also provide an easier interface for commenting and suggesting changes.+1 to migrating to something that makes it easier to see comments vs. the document.
Another idea would be to code it in asciidoc and submit it as a PR to it's final resting place. This way we have somethign to refer to when we submit it for various approvals and you can make line-by-line comments.
Having a more readable draft would help me with getting Flock as in compliance as it can be.
I have not yet migrated it yet, so there is flexibility.
What is easiest for you in regards to Flock: AsciiDoc or a Google Doc? I will have enough time to migrate it once, but probably only once before Flock. I'd prefer to put it into the format that is easiest for you to review any suggestions offered there.
On Thu, Jul 26, 2018 at 3:03 PM, Justin W. Flory jflory7@gmail.com wrote:
On 07/24/2018 06:59 AM, Brian (bex) Exelbierd wrote:
On Thu, Jul 19, 2018 at 11:47 PM, Justin W. Flory <jflory7@gmail.com mailto:jflory7@gmail.com> wrote:
Hi all, I am proposing to migrate the event guidelines into a Google Doc to provide a single place to point people (with authenticated protection and commenting) and also provide an easier interface for commentingand
suggesting changes.+1 to migrating to something that makes it easier to see comments vs. the document.
Another idea would be to code it in asciidoc and submit it as a PR to it's final resting place. This way we have somethign to refer to when we submit it for various approvals and you can make line-by-line
comments.
Having a more readable draft would help me with getting Flock as in compliance as it can be.
I have not yet migrated it yet, so there is flexibility.
What is easiest for you in regards to Flock: AsciiDoc or a Google Doc? I will have enough time to migrate it once, but probably only once before Flock. I'd prefer to put it into the format that is easiest for you to review any suggestions offered there.
Both are fine with me. Neither helps my need to use it like a tick-list for Flock.
regards,
bex
-- Cheers, Justin W. Flory jflory7@gmail.com
Fedora Diversity & Inclusion Team mailing list -- diversity@lists.fedoraproject.org To unsubscribe send an email to diversity-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/diversity@ lists.fedoraproject.org/message/RY2S2G7R6KWZOW7SZLGIGAIHYDWABNBE/
The Etherpad is migrated:
https://docs.google.com/document/d/1PQVkafUUZUuVAEqJZ1aFrAy3ce7DYXYhj-Mf4Qvx...
Please take a review when possible. This should make it easier to solicit feedback and have conversation about pieces of the document.
On 07/26/2018 09:01 AM, Brian (bex) Exelbierd wrote:
On Thu, Jul 26, 2018 at 3:03 PM, Justin W. Flory <jflory7@gmail.com mailto:jflory7@gmail.com> wrote:
On 07/24/2018 06:59 AM, Brian (bex) Exelbierd wrote: > > On Thu, Jul 19, 2018 at 11:47 PM, Justin W. Flory <jflory7@gmail.com <mailto:jflory7@gmail.com> > <mailto:jflory7@gmail.com <mailto:jflory7@gmail.com>>> wrote: > > Hi all, > > I am proposing to migrate the event guidelines into a Google Doc to > provide a single place to point people (with authenticated protection > and commenting) and also provide an easier interface for commenting and > suggesting changes. > > > +1 to migrating to something that makes it easier to see comments vs. > the document. > > Another idea would be to code it in asciidoc and submit it as a PR to > it's final resting place. This way we have somethign to refer to when > we submit it for various approvals and you can make line-by-line comments. > > Having a more readable draft would help me with getting Flock as in > compliance as it can be. > I have not yet migrated it yet, so there is flexibility. What is easiest for you in regards to Flock: AsciiDoc or a Google Doc? I will have enough time to migrate it once, but probably only once before Flock. I'd prefer to put it into the format that is easiest for you to review any suggestions offered there.Both are fine with me. Neither helps my need to use it like a tick-list for Flock.
regards,
bex
-- Cheers, Justin W. Flory jflory7@gmail.com <mailto:jflory7@gmail.com> _______________________________________________ Fedora Diversity & Inclusion Team mailing list -- diversity@lists.fedoraproject.org <mailto:diversity@lists.fedoraproject.org> To unsubscribe send an email to diversity-leave@lists.fedoraproject.org <mailto:diversity-leave@lists.fedoraproject.org> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html <https://getfedora.org/code-of-conduct.html> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines <https://fedoraproject.org/wiki/Mailing_list_guidelines> List Archives: https://lists.fedoraproject.org/archives/list/diversity@lists.fedoraproject.org/message/RY2S2G7R6KWZOW7SZLGIGAIHYDWABNBE/ <https://lists.fedoraproject.org/archives/list/diversity@lists.fedoraproject.org/message/RY2S2G7R6KWZOW7SZLGIGAIHYDWABNBE/>-- Brian (bex) Exelbierd | bexelbie@redhat.com mailto:bexelbie@redhat.com | bex@pobox.com mailto:bex@pobox.com Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org
Fedora Diversity & Inclusion Team mailing list -- diversity@lists.fedoraproject.org To unsubscribe send an email to diversity-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/diversity@lists.fedoraproject....
diversity@lists.fedoraproject.org
-
Brian (bex) Exelbierd -
Justin W. Flory