Hmm

I have started one that seems to be a private project, but I have made it
visible to anyone [1]. I hope that means anyone can add cards to the
leftmost column.

[1] https://github.com/users/cottage14/projects/1

On Wed, Dec 11, 2019 at 2:30 PM Josh Tynjala <[email protected]>
wrote:

> I'm not really familiar with Confluence, but I think that your best bet on
> Github is to use Project boards:
>
>
> https://help.github.com/en/github/managing-your-work-on-github/managing-project-boards
>
> --
> Josh Tynjala
> Bowler Hat LLC <https://bowlerhat.dev>
>
>
> On Wed, Dec 11, 2019 at 10:19 AM Andrew Wetmore <[email protected]>
> wrote:
>
> > On the specifics of the Layouts information page from FlexJS, where
> should
> > it go? In the Royale help docs I see a "_layouts" folder that has an HTML
> > page (not markdown). Is this part of the help documentation, or some
> other
> > thing? Shall I put it in user-interface?
> >
> > If people know of some high-value ckwiki pages that should migrate,
> please
> > let me know. I will create a list (ah: this is the sort of thing that
> > Confluence can handle; how does GitHub deal with it?) and work through
> the
> > pages.
> >
> > Andrew
> >
> > On Wed, Dec 11, 2019 at 2:12 PM Andrew Wetmore <[email protected]>
> > wrote:
> >
> > > Hm. I cannot log in to the Flex Confluence because I am not a Flex
> > > committer. I can probably copy the content of topics, but I am not sure
> > > what other problems this restriction will create.
> > >
> > > a
> > >
> > > On Wed, Dec 11, 2019 at 2:09 PM Andrew Wetmore <[email protected]>
> > > wrote:
> > >
> > >> Is there an equivalent to Confluence in GitHub?
> > >>
> > >> On Wed, Dec 11, 2019 at 2:00 PM Carlos Rovira <
> [email protected]>
> > >> wrote:
> > >>
> > >>> Hi Andrew,
> > >>>
> > >>> for me cwiki and other flex things was the "old way". In Royale we
> use
> > >>> GitHub tools. So the Github wiki is like the Apache cwiki
> > >>> Don't need to have the old tools, we even talked about that long time
> > ago
> > >>> and decided to go Github way since is what all people are using
> today.
> > >>>
> > >>> One thing you can do is migrate things from FlexJS already not
> migrated
> > >>> to
> > >>> Royale Docs, for example this page (to take one):
> > >>>
> > >>> https://cwiki.apache.org/confluence/display/FLEX/FlexJS+Layout
> > >>>
> > >>> That content should have an entry in Royale Docs in Features part
> > (Royale
> > >>> Layouts). And other here should review if contents need some updating
> > >>> But as a starting point I think is ok, changing "FlexJS" for
> ·"Royale",
> > >>> and
> > >>> things like that.
> > >>>
> > >>> Thanks
> > >>>
> > >>> Carlos
> > >>>
> > >>>
> > >>>
> > >>> El mié., 11 dic. 2019 a las 18:49, Andrew Wetmore (<
> > [email protected]
> > >>> >)
> > >>> escribió:
> > >>>
> > >>> > Hi:
> > >>> >
> > >>> > I gather from Infra that Royale does not have its own cwiki (and
> not
> > >>> its
> > >>> > own Confluence??) account. The person I was speaking with suggested
> > we
> > >>> > should have our own, rather than piggybacking on the Flex cwiki,
> not
> > >>> least
> > >>> > because committers like me (a committer for Royale but not for
> Flex)
> > >>> can
> > >>> > run into problems, as when I could not edit the board report in
> > >>> Confluence
> > >>> > today.
> > >>> >
> > >>> > How do we get this organized? I would be happy to help migrate from
> > the
> > >>> > Flex cwiki everything that is there that also or primarily applies
> to
> > >>> > Royale.
> > >>> >
> > >>> > Andrew
> > >>> >
> > >>> > --
> > >>> > Andrew Wetmore
> > >>> >
> > >>> > http://cottage14.blogspot.com/
> > >>> >
> > >>>
> > >>>
> > >>> --
> > >>> Carlos Rovira
> > >>> http://about.me/carlosrovira
> > >>>
> > >>
> > >>
> > >> --
> > >> Andrew Wetmore
> > >>
> > >> http://cottage14.blogspot.com/
> > >>
> > >>
> > >>
> > >>
> > >>
> > >
> > > --
> > > Andrew Wetmore
> > >
> > > http://cottage14.blogspot.com/
> > >
> > >
> > >
> > >
> > >
> >
> > --
> > Andrew Wetmore
> >
> > http://cottage14.blogspot.com/
> >
>


-- 
Andrew Wetmore

http://cottage14.blogspot.com/

Reply via email to