I would like to circle this around to an older conversation around the RFC
process. We chose to use the ASF wiki and email over using repo and PR process.
If we move more things over to GitHub I think that warrants a rethink. RFC
conversations have been split between email and wiki comments. Usi
Looks like we can use the `.asf.yml` file in our repositories to enable
`issues` and `wiki` behavior ourselves if we decide we like the feature :)
On Fri, Apr 24, 2020 at 7:46 AM Dave Barnes wrote:
> +1
> I like the look of the samples.
> I also want to echo Anthony and Blake: Accessibility is h
+1
I like the look of the samples.
I also want to echo Anthony and Blake: Accessibility is huge, not only because
it smooths the way for adding content, but for pruning outdated material.
On 4/24/20, 7:18 AM, "Blake Bender" wrote:
+1 - Wow, research - nice work, Naba, this is great!
J
+1 - Wow, research - nice work, Naba, this is great!
Just want to emphasize a larger point I failed to make in my response re:
Markdown. My experience with Wikis has been that it's very difficult to
convince people to contribute entries/edits, and an active community of
contributors makes a big d
Hi Anthony!
Sorry for the late reply but I was doing some research. The issues and wiki
section as of now has been used by few engineers only and Confluent has not
yet entered any issues as they are still reviewing the project. I went
ahead and looked into all projects in the Apache domain using i
How about keeping things in the GitHub wiki that are very tightly couple to the
use of that repo? Like style guides? Building guides? Eh... does ASF have any
input on using the GitHub wiki over the ASF wiki?
> On Apr 23, 2020, at 2:40 PM, Anthony Baker wrote:
>
> Having used pretty every styl
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 augme
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 wrote:
> Naba, do you have any updates to share? I’m curious if you have found
> this useful compared to JIRA.
>
> Also, I notic
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
+1!
On Sat, Mar 21, 2020, 17:17 Nabarun Nag 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
> act
+1 !!
-michael
On Mon, Mar 23, 2020 at 8:33 AM Aaron Lindsey
wrote:
> YES +1
>
> > On Mar 23, 2020, at 7:42 AM, Bruce Schuchardt
> wrote:
> >
> > +1
> >
> > On 3/21/20, 5:17 PM, "Nabarun Nag" wrote:
> >
> >Hello team,
> >
> >We are planning to experiment with usin
YES +1
> On Mar 23, 2020, at 7:42 AM, Bruce Schuchardt wrote:
>
> +1
>
> On 3/21/20, 5:17 PM, "Nabarun Nag" 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). Pleas
+1
On 3/21/20, 5:17 PM, "Nabarun Nag" 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
+1
It will be easier to contribute to Geode if you just need a github account.
De: Ju@N
Enviado: lunes, 23 de marzo de 2020 11:13
Para: dev@geode.apache.org
Asunto: Re: [VOTE] Using Github issues and wiki for geode-kafka-connector
project
+1
On Sun, 22 Mar
+1
On Sun, 22 Mar 2020 at 16:26, Jacob Barrett wrote:
>
>
> > On Mar 22, 2020, at 9:23 AM, Anthony Baker wrote:
> >
> > Check out [1] for a list of projects that are moving to GitHub issues.
> As long as the PMC approves, INFRA will support the switch.
>
>
> Awesome!!
>
> > Once we see how tha
> On Mar 22, 2020, at 9:23 AM, Anthony Baker wrote:
>
> Check out [1] for a list of projects that are moving to GitHub issues. As
> long as the PMC approves, INFRA will support the switch.
Awesome!!
> Once we see how that goes, I’m in favor of having a larger conversation about
> migrat
Check out [1] for a list of projects that are moving to GitHub issues. As long
as the PMC approves, INFRA will support the switch.
(Side note: kinda ironic that you have to file a JIRA to move to GitHub issues
:-)
+1 for experimenting with the geode-kafka-connector repo.
Once we see how that
+1 couldn’t be anymore onboard with this. Maybe I missed a discussion about
this earlier but are we certain that ASF rules allow for this? I would think as
long as all the notifications go through the the mailing lists and gitbox is
setup they would be ok. Just given that neither of your example
+1
-Dan
On Sat, Mar 21, 2020, 9:48 PM Udo Kohlmeyer wrote:
> +1
>
> On 3/21/20 5:16 PM, Nabarun Nag 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
+1
On 3/21/20 5:16 PM, Nabarun Nag 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
+1
> On Mar 21, 2020, at 5:16 PM, Nabarun Nag 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
21 matches
Mail list logo
