From: Aseem Prashar <prashara-e/prDBdGCFNcusGGlJDZ6w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Inclusivity Issues for new contributors
Date: Tue, 21 May 2019 10:44:54 -0700 (PDT) [thread overview]
Message-ID: <7231afe1-fd0a-4e7d-93ce-fadb9030a244@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1774 bytes --]
Hi everyone!
Oregon State University's Free/Open Source Software class has us evaluate
real-world open-source projects for inclusivity using a cognitive
walk-through technique.
I am opening this discussion thread to facilitate conversation on
inclusivity within the Pandoc project.
*Issue 1:* Our cognitive walk-through found that contributing to Pandoc
page (https://github.com/jgm/pandoc/blob/master/CONTRIBUTING.md) doesn’t
give enough information
on how to set up the environment and start contributing to people who are
new to open source to encourage them to contribute to this project.
*Issue 2:* The documentation should also provide more instructions on
setting up the test environment as most people contributing to open source
for the first time will not be familiar with
the testing methods used. The documentation on what kind of test is done
and how to test new features should also be included.
*Issue 3: *This tool is mainly for front end developers, but it has been
implemented as a command line program, making a GUI for the tool will make
using this tool easier and faster.
Thank you for reading, looking forward to your responses.
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/7231afe1-fd0a-4e7d-93ce-fadb9030a244%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 2324 bytes --]
next reply other threads:[~2019-05-21 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 17:44 Aseem Prashar [this message]
[not found] ` <7231afe1-fd0a-4e7d-93ce-fadb9030a244-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-05-21 19:02 ` Lukas Atkinson
2019-05-22 0:13 ` Kolen Cheung
[not found] ` <6b58c3f2-ba94-4f0d-8e3f-3c3bf4c71c73-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-05-22 16:36 ` John MacFarlane
2019-05-22 9:36 ` BPJ
2019-05-22 17:57 ` mb21
2019-06-03 21:00 ` CR
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7231afe1-fd0a-4e7d-93ce-fadb9030a244@googlegroups.com \
--to=prashara-e/prdbdgcfncusggljdz6w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).