So you'd like a devdoc component for JBDS even though my goal is
to
move all that doc to the jbosstools-devdoc repo? There really aren't
any internal details in there any more except some email addresses and
a couple of ssh paths (which we have doc'd in other public scripts
already, eg., in jbosstools-build-ci).
we don't open issues in JBIDE that has to do with JBDS specific things;
not sure why
we would start doing that for devdoc stuff.
Which components would you use for adding developer focused
documentation for the installer (for example)
or the product features ?
Seems illogical to create a component that won't ever be used /
is
already deprecated.
--
And yes, IMHO, there's a difference between devdoc (for devs) and
documentation (for end users). If there was no difference, we wouldn't
have two github repos:
https://github.com/jbosstools/jbosstools-devdoc
https://github.com/jbosstools/jbosstools-documentation
Therefore, we should have 2 JBIDE components, to match what's in
github.
our components don't 100% align up with github repos.
jbosstools-documentation have not been used in ages now (not since JBDS
7 afaik).
/max
On Fri, Oct 2, 2015 at 4:41 AM, Max Rydahl Andersen
<manderse(a)redhat.com> wrote:
> do we really need both devdoc and documentation component ?
>
> in any case, I would say life is simpler if we have components in
> JBIDE that
> we also have in JBDS ....
>
> /max
>
>> FYI, I've added a new component to JBIDE JIRA: devdoc.
>>
>> This is because having everything in "build" isn't always
accurate.
>> Hopefully this will also encourage me, Mickael, Paul, Max, Alexey,
>> Denis, etc. to write & update more developer documentation so our
>> process documents stay current, even as they're evolving &
>> improving.
>>
>>
>>
https://issues.jboss.org/browse/JBIDE/component/12322530/?selectedTab=com...
>>
>> I haven't created a matching component in JBDS yet, since most
>> devdoc
>> is in
https://github.com/jbosstools/jbosstools-devdoc - we only use
>>
https://github.com/jbdevstudio/jbdevstudio-devdoc for the release
>> guide, which other than some internal server details could
>> potentially
>> be moved to the JBT side of the house.
>>
>> Comments, feedback, brickbats & new issues under this component
>> welcome.
>>
>> --
>> Nick Boldt :: JBoss by Red Hat
>> Productization Lead :: JBoss Tools & Dev Studio
>>
http://nick.divbyzero.com
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
>
> /max
>
http://about.me/maxandersen
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
/max
http://about.me/maxandersen