Having used pretty every style of wiki, I care less about the wiki tech and more about making the content easily accessible and discoverable for our users and contributors. Our current wiki has a lot of useful information. I’d like to understand how we want to use repo-specific wiki’s to augment or replace our current project wiki (or neither)\ before taking any decisions.
Anthony > On Apr 23, 2020, at 12:54 PM, Blake Bender <bben...@pivotal.io> wrote: > > GitHub Wiki supports Markdown, our current one does not. This means GitHub > wins by default in my book. > > Thanks, > > Blake > > > On Thu, Apr 23, 2020 at 8:50 AM Anthony Baker <aba...@pivotal.io> wrote: > >> Naba, do you have any updates to share? I’m curious if you have found >> this useful compared to JIRA. >> >> Also, I noticed that geode-kafka-connector also has a GitHub wiki. How >> does that compare with centralizing our information in the ASF confluence >> wiki? >> >> Thanks, >> Anthony >> >> >>> On Mar 21, 2020, at 5:16 PM, Nabarun Nag <n...@apache.org> wrote: >>> >>> Hello team, >>> >>> We are planning to experiment with using Github issues and wiki for the >>> Apache project *Geode-Kafka-Connector. *(not Apache Geode project). >> Please >>> do give your vote on this as we need to send the vote link to infra to >>> activate it. >>> >>> *Why are we doing this ? / Advantages* : >>> 1. *Unified location* to have documentation, code and issue tracking. >>> 2. Leverage Github tools like Github pages to create websites hosting >>> information about the project. >>> 3. No separate JIRA accounts or permission required to create issues. >>> 4. This will have *no impact on the broader Geode community* as right now >>> only 3-4 developers involved in this project. >>> 5. *This is an experiment.* If things do not work out we can always >> revert >>> back to the traditional way of having separate JIRA, documentation, >>> websites etc. >>> >>> *Precedence*: >>> 1. Kubernetes uses the github issues >>> 2. RabbitMQ uses github issues. >>> >>> >>> *NOTE: *- Please be cordial and do not use any condescending language and >>> absolutely no bullying. >>> - Please treat this email as a professional business email and maintain >>> email etiquette while replying. >>> >>> Regards >>> Nabarun >> >>
