hey Bryan -- I just enabled "Add/Edit" permission for all registered
Confluence users. Let me know if it works now

On Thu, Jul 12, 2018 at 1:34 PM, Bryan Cutler <cutl...@gmail.com> wrote:
> I haven't used confluence before, but do I need permission to edit a page?
> I believe there should be a button in the menu bar, but I don't see
> anything except "Spaces" and "People." If so, could someone please add me,
> my user id is "cutlerb", thanks!
>
> On Fri, Jul 6, 2018 at 10:35 AM, Wes McKinney <wesmck...@gmail.com> wrote:
>
>> I've started building out some organization on the Arrow wiki landing
>> page. I think something we can do to help keep organized is to use a
>> combination of Component and Label tags in JIRA, then add JIRA filters
>> to pages related to each subproject. We can see how that goes
>>
>> As an example, I just created a page to track work on Parquet support in
>> Python:
>>
>> https://cwiki.apache.org/confluence/display/ARROW/
>> Python+Parquet+Format+Support
>>
>> As we add more issues labels, they'll show up in the filter.
>>
>> - Wes
>>
>> On Fri, Jun 29, 2018 at 6:38 PM, Kouhei Sutou <k...@clear-code.com> wrote:
>> > Hi,
>> >
>> >> https://cwiki.apache.org/confluence/display/ARROW
>> >>
>> >> If any PMC members would like to be administrators of the space,
>> >> please let me know your Confluence username. You have to create a
>> >> separate account (it does not appear to be linked to JIRA accounts)
>> >
>> > Can you add me? I've created "kou" account on Confluence.
>> >
>> >
>> > Thanks,
>> > --
>> > kou
>> >
>> > In <CAJPUwMAxYDUKKS9qLCqCbb1OJGnk2XJ-3fFS=nvm43ks40u...@mail.gmail.com>
>> >   "Re: Housing longer-term Arrow development, design, and roadmap
>> documents" on Tue, 26 Jun 2018 11:27:50 -0400,
>> >   Wes McKinney <wesmck...@gmail.com> wrote:
>> >
>> >> GitHub wiki pages lack collaboration features like commenting. It will
>> >> be interesting to see what we can work up with JIRA integration, e.g.
>> >> burndown charts for release management.
>> >>
>> >> I asked INFRA to create a Confluence space for us so we can give it a
>> >> try to see if it works for us. Confluence seems to have gotten a lot
>> >> nicer since I last used it:
>> >>
>> >> https://cwiki.apache.org/confluence/display/ARROW
>> >>
>> >> If any PMC members would like to be administrators of the space,
>> >> please let me know your Confluence username. You have to create a
>> >> separate account (it does not appear to be linked to JIRA accounts)
>> >>
>> >> Thanks
>> >>
>> >> On Sun, Jun 24, 2018 at 1:14 PM, Uwe L. Korn <uw...@xhochy.com> wrote:
>> >>> Hello,
>> >>>
>> >>> I would prefer Confluence over GitHub pages because I would hope that
>> one can integrate the ASF JIRA via widgets into the wiki pages. The vast
>> amount of issues should all be categorizable into some topic. Once these
>> are triaged, they should pop up in the respective wiki pages that could
>> form a roadmap. That way, newcomers should get a better start to find the
>> things to work on for a certain topic.
>> >>>
>> >>> Cheers
>> >>> Uwe
>> >>>
>> >>> On Sun, Jun 24, 2018, at 7:02 PM, Antoine Pitrou wrote:
>> >>>>
>> >>>> Hi Wes,
>> >>>>
>> >>>> I wonder if GitHub wiki pages would be an easier-to-approach
>> alternative?
>> >>>>
>> >>>> Regards
>> >>>>
>> >>>> Antoine.
>> >>>>
>> >>>>
>> >>>> Le 24/06/2018 à 08:42, Wes McKinney a écrit :
>> >>>> > hi folks,
>> >>>> >
>> >>>> > Since the scope of Apache Arrow has grown significantly in the last
>> >>>> > 2.5 years to encompass many programming languages and new areas of
>> >>>> > functionality, I'd like to discuss how we could better accommodate
>> >>>> > longer-term asynchronous discussions and stay organized about the
>> >>>> > development roadmap.
>> >>>> >
>> >>>> > At any given time, there could be 10 or more initiatives ongoing,
>> and
>> >>>> > the number of concurrent initiatives is likely to continue
>> increasing
>> >>>> > over time as the community grows larger. Just off the top of my head
>> >>>> > here's some stuff that's ongoing / up in the air:
>> >>>> >
>> >>>> > * Remaining columnar format design questions (interval types,
>> unions, etc.)
>> >>>> > * Arrow RPC client/server design (aka "Arrow Flight")
>> >>>> > * Packaging / deployment / release management
>> >>>> > * Rust language build out
>> >>>> > * Go language build out
>> >>>> > * Code generation / LLVM (Gandiva)
>> >>>> > * ML/AI framework integration (e.g. with TensorFlow, PyTorch)
>> >>>> > * Plasma roadmap
>> >>>> > * Record data types (thread I just opened)
>> >>>> >
>> >>>> > With ~500 open issues on JIRA, I have found that newcomers feel a
>> bit
>> >>>> > overwhelmed when they're trying to find a part of the project to get
>> >>>> > involved with. Eventually one must sink one's teeth into the JIRA
>> >>>> > backlog, but I think it would be helpful to have some centralized
>> >>>> > project organization and roadmap documents to help navigate all of
>> the
>> >>>> > efforts going on in the project.
>> >>>> >
>> >>>> > I don't think documents in the repository are a great solution for
>> >>>> > this, as they don't facilitate discussions very easily --
>> >>>> > documentation or Markdown documents (like the columnar format
>> >>>> > specification) are good to write there when some decisions have been
>> >>>> > made. Google Documents are great, but they are somewhat ephemeral.
>> >>>> >
>> >>>> > I would suggest using the ASF's Confluence wiki for these purposes.
>> >>>> > The Confluence UI is a bit clunky like other Atlassian products, but
>> >>>> > the wiki-style model (central landing page + links to subprojects)
>> and
>> >>>> > collaboration features (comments and discussions on pages) would
>> give
>> >>>> > us what we need. I suspect that it integrates with JIRA also, which
>> >>>> > would help with cross-references to particular concrete JIRA items
>> >>>> > related to subprojects. Here's an example of a Confluence landing
>> page
>> >>>> > for another ASF project:
>> >>>> > https://cwiki.apache.org/confluence/display/Impala
>> >>>> >
>> >>>> > What do others think?
>> >>>> >
>> >>>> > Thanks,
>> >>>> > Wes
>> >>>> >
>>

Reply via email to