Neither you nor JB was setup to be able to do anything with the Wiki. I just enabled JB and yourself (assume “kenn” is you) to have permission to administer the space so you should be able to add other people.
Dan > On Jun 9, 2018, at 9:57 AM, Kenneth Knowles <k...@google.com> wrote: > > Yea, we have one but it seems to not be set up quite right. JB you are the > admin from the original incubation. Can you check the permissions? Also make > some more admins (maybe all the PMC to start with). I would like to help out. > > https://cwiki.apache.org/confluence/display/BEAM/ > <https://cwiki.apache.org/confluence/display/BEAM/> > https://issues.apache.org/jira/browse/INFRA-11181 > <https://issues.apache.org/jira/browse/INFRA-11181> > > > Kenn > > On Fri, Jun 8, 2018 at 10:12 PM Jean-Baptiste Onofré <j...@nanthrax.net > <mailto:j...@nanthrax.net>> wrote: > +1 > > That's funny, because AFAIR, it's what we discussed in the early stage > of the project. > We can also link wiki pages on the website if we want to provide details. > AFAIR, we already have a confluence wiki space for Beam. > > Regards > JB > > On 07/06/2018 22:23, Kenneth Knowles wrote: > > Hi all, > > > > I've been in half a dozen conversations recently about whether to have a > > wiki and what to use it for. Some things I've heard: > > > > - "why is all this stuff that users don't care about here?" > > - "can we have a lighter weight place to put technical references for > > contributors" > > > > So I want to consider as a community starting up our wiki. Ideas for > > what could go there: > > > > - Collection of links to design docs like > > https://beam.apache.org/contribute/design-documents/ > > <https://beam.apache.org/contribute/design-documents/> > > - Specialized walkthroughs > > like https://beam.apache.org/contribute/docker-images/ > > <https://beam.apache.org/contribute/docker-images/> > > - Best-effort notes that just try to help out > > like https://beam.apache.org/contribute/intellij/ > > <https://beam.apache.org/contribute/intellij/> > > - Docs on in-progress stuff > > like https://beam.apache.org/documentation/runners/jstorm/ > > <https://beam.apache.org/documentation/runners/jstorm/> > > - Expanded instructions for committers, more > > than https://beam.apache.org/contribute/committer-guide/ > > <https://beam.apache.org/contribute/committer-guide/> > > - BIPs / summaries of collections of JIRA > > - Docs sitting in markdown in the repo > > like https://github.com/apache/beam/blob/master/sdks/CONTAINERS.md > > <https://github.com/apache/beam/blob/master/sdks/CONTAINERS.md> > > and https://github.com/apache/beam-site/blob/asf-site/README.md > > <https://github.com/apache/beam-site/blob/asf-site/README.md> (which > > will soon not be a toplevel README) > > > > What do you think? > > > > (a) should we do it? > > (b) what should go there? > > (c) what should not go there? > > > > Kenn > > -- > Jean-Baptiste Onofré > jbono...@apache.org <mailto:jbono...@apache.org> > http://blog.nanthrax.net <http://blog.nanthrax.net/> > Talend - http://www.talend.com <http://www.talend.com/> -- Daniel Kulp dk...@apache.org <mailto:dk...@apache.org> - http://dankulp.com/blog <http://dankulp.com/blog> Talend Community Coder - http://coders.talend.com <http://coders.talend.com/>
