using a self built incubator netbeans current git checkout

2018-01-27 Thread Gary Bello 
Every few days I update and build current git repo of incubator netbeans.

I then configure to run with jdk9.

There are a lot of plugin options to choose from -
do we know how safe/reliable/bug-free the available plugins are at this
time ?

or which of the avail plugins should only be used at this time?

Recently I added a bunch of plugins and then noticed some problems - for
instance I could not get tools/options panel to open.

Thank
-Gary

Re: ***UNCHECKED*** github wiki experiment

2018-01-27 Thread Antonio 



On 27/01/18 18:51, Neil C Smith wrote:

On Sat, 27 Jan 2018 at 16:41 Antonio  wrote:


Then could restrict wiki editing to the team, using the editor for
ourselves, and allow the world to submit PRs against 'X'.



If we're doing that and not allowing wider permissions, I don't see that we
gain much by adding cloning between.   Surely we can just run a standard
repo and forget the GH wiki specifically - we can still edit online.  The
only thing we really lose is the toolbar, but that was more with wider
access in mind - if we're doing PRs then doesn't seem much point.


So we leave the wiki as is, right? (I'm confused)



If we find we want a better UI later, there are options (like Netlify CMS,
but also others).  Mind you, not sure if any support asciidoc over markdown
- was there a particular reason you went with that?



asciidoc seems more standard than markdown. Tables, for instance, are an 
extension to markdown, but are native in asciidoc. asciidoc can also be 
transformed to docbook & epub more easily, I think.



Best wishes,

Neil



Cheers,
Antonio

P.S.: I don't recall adding the 'UNCHECKED' stuff in the subject of the 
thread. I think either my email client or the mailing list daemon assume 
I'm an "unchecked" person or something O_o.






-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

License handling (was: Re: Ready to vote on Apache NetBeans (incubating) 9.0 Beta RC3?)

2018-01-27 Thread Matthias Bläsing 
Hi Jan,

Am Samstag, den 27.01.2018, 17:21 +0100 schrieb Jan Lahoda:
> On Sat, Jan 27, 2018 at 3:20 PM, Matthias Bläsing  > wrote:
> > Hi Jan,
> > 
> > Am Samstag, den 27.01.2018, 15:12 +0100 schrieb Jan Lahoda:
> > > 
> > > Does this relate only to things we have in source, or also to external
> > > binaries?
> > 
> > I'm only looking into the files in the repository. I'm touching the
> > CreateLicenseSummary and VerifyLibsAndLicenses tasks for this.
> > 
> 
> Cool. For the maven (and probably a few more similar jars), I so far also
> have a tweak for CreateLicenseSummary:
> ---
> diff --git
> a/nbbuild/antsrc/org/netbeans/nbbuild/extlibs/CreateLicenseSummary.java
> b/nbbuild/antsrc/org/netbeans/nbbuild/extlibs/CreateLicenseSummary.java
> index da4f169..b4cef9b 100644
> --- a/nbbuild/antsrc/org/netbeans/nbbuild/extlibs/CreateLicenseSummary.java
> +++ b/nbbuild/antsrc/org/netbeans/nbbuild/extlibs/CreateLicenseSummary.java
> @@ -253,9 +253,11 @@ public class CreateLicenseSummary extends Task {
>  if (!innerName.endsWith(".jar") && 
> !innerName.endsWith(".zip")) {
>  continue;
>  }
> +Map nestedHeaders = 
> binary2License.get(n + "!/" + innerName);
> +if (nestedHeaders == null) nestedHeaders = 
> headers;
>  is = zf.getInputStream(entry);
>  try {
> -crc2LicenseHeaders.put(computeCRC32(is), 
> headers);
> +crc2LicenseHeaders.put(computeCRC32(is), 
> nestedHeaders);
>  } finally {
>  is.close();
>  }
>  ---
> 
> Would that fit into what you are doing? (The intent is basically to allow
> the -license.txt files to say something like:
> Files: apache-maven-3.3.9-bin.zip!/apache-maven-3.3.9/lib/jsr250-api-1.0.jar
> 
> to refer to a file that is inside an external binary zip/jar.
> 

If I'm not mistaken, the syntax you are using is the way nested
resources are addressed in the java API. Sounds good and sensible to
me.

Your work may conflict with my changes on the source level (I did some
rearranging), but should not conflict with the general changes.

I think I got the changeset into a workable state and pushed it to
github:

https://github.com/apache/incubator-netbeans/pull/396

This is not the complete solution, but from my perspective should give
us a solid start.


Greetings

Matthias

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: ***UNCHECKED*** github wiki experiment

2018-01-27 Thread Neil C Smith 
On Sat, 27 Jan 2018 at 16:41 Antonio  wrote:

> Then could restrict wiki editing to the team, using the editor for
> ourselves, and allow the world to submit PRs against 'X'.
>

If we're doing that and not allowing wider permissions, I don't see that we
gain much by adding cloning between.   Surely we can just run a standard
repo and forget the GH wiki specifically - we can still edit online.  The
only thing we really lose is the toolbar, but that was more with wider
access in mind - if we're doing PRs then doesn't seem much point.

If we find we want a better UI later, there are options (like Netlify CMS,
but also others).  Mind you, not sure if any support asciidoc over markdown
- was there a particular reason you went with that?

Best wishes,

Neil


-- 
Neil C Smith
Artist & Technologist
www.neilcsmith.net

Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org

Re: ***UNCHECKED*** github wiki experiment

2018-01-27 Thread Antonio 



On 27/01/18 17:04, Neil C Smith wrote:

On Fri, 26 Jan 2018 at 17:56 Neil C Smith  wrote:


I still haven't heard anything back from my email to infra@ to see
whether GitBox can handle syncing the wiki repo.



OK, had a reply on infra@.  It looks like GitHub wikis are backed up via
GitBox, but that it's hidden and (I think, asked for clarification) the git
repo isn't accessible from the Apache side.  This might be another argument
in favour of just using a standard repo for the wiki?  We'd lose some
benefits though ...



And what about using a standard github repo 'X' for the wiki, so that 
Apache infra can back up that through GitBox etc...


And then make the 'X.wiki.git' _a clone_ of 'X'? This is, make 
'X.wiki.git' remote's be 'X'?


Then could restrict wiki editing to the team, using the editor for 
ourselves, and allow the world to submit PRs against 'X'.


Maybe we want to test that setup, right? I may give it a run later.

Cheers,
Antonio


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Ready to vote on Apache NetBeans (incubating) 9.0 Beta RC3?

2018-01-27 Thread Jan Lahoda 
On Sat, Jan 27, 2018 at 3:20 PM, Matthias Bläsing  wrote:

> Hi Jan,
>
> Am Samstag, den 27.01.2018, 15:12 +0100 schrieb Jan Lahoda:
> >
> > Does this relate only to things we have in source, or also to external
> > binaries?
>
> I'm only looking into the files in the repository. I'm touching the
> CreateLicenseSummary and VerifyLibsAndLicenses tasks for this.
>

Cool. For the maven (and probably a few more similar jars), I so far also
have a tweak for CreateLicenseSummary:
---
diff --git
a/nbbuild/antsrc/org/netbeans/nbbuild/extlibs/CreateLicenseSummary.java
b/nbbuild/antsrc/org/netbeans/nbbuild/extlibs/CreateLicenseSummary.java
index da4f169..b4cef9b 100644
--- a/nbbuild/antsrc/org/netbeans/nbbuild/extlibs/CreateLicenseSummary.java
+++ b/nbbuild/antsrc/org/netbeans/nbbuild/extlibs/CreateLicenseSummary.java
@@ -253,9 +253,11 @@ public class CreateLicenseSummary extends Task {
 if (!innerName.endsWith(".jar") &&
!innerName.endsWith(".zip")) {
 continue;
 }
+Map nestedHeaders =
binary2License.get(n + "!/" + innerName);
+if (nestedHeaders == null) nestedHeaders =
headers;
 is = zf.getInputStream(entry);
 try {
-crc2LicenseHeaders.put(computeCRC32(is),
headers);
+crc2LicenseHeaders.put(computeCRC32(is),
nestedHeaders);
 } finally {
 is.close();
 }
 ---

Would that fit into what you are doing? (The intent is basically to allow
the -license.txt files to say something like:
Files: apache-maven-3.3.9-bin.zip!/apache-maven-3.3.9/lib/jsr250-api-1.0.jar

to refer to a file that is inside an external binary zip/jar.


> > We are not attributing certain jars properly (e.g. some jars
> > embedded in Apache Maven are not under Apache License 2.0, even though
> our
> > license file says so). So I was peeking at that a little (we could
> enhance
> > the *-license.txt format to also accept files from inside of jars, and
> then
> > it would hopefully all work OK).
>
> Sounds good - and good catch.
>

Actually, it was noted in one of the Justin's e-mails.

Thanks,
Jan


>
> Matthias
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: ***UNCHECKED*** github wiki experiment

2018-01-27 Thread Neil C Smith 
On Fri, 26 Jan 2018 at 17:56 Neil C Smith  wrote:

> I still haven't heard anything back from my email to infra@ to see
> whether GitBox can handle syncing the wiki repo.
>

OK, had a reply on infra@.  It looks like GitHub wikis are backed up via
GitBox, but that it's hidden and (I think, asked for clarification) the git
repo isn't accessible from the Apache side.  This might be another argument
in favour of just using a standard repo for the wiki?  We'd lose some
benefits though ...

>
> If we want PR then this might be a better way to go.  On the other hand,
> we're limited to the permissions on the repository, although if we use a
> separate repository just for the wiki that may not be a problem.  We also
> know that standard repositories sync to Apache.  Other issue is the editing
> UI on the GitHub side isn't quite as nice - missing the toolbar.
>

For unrelated reasons I was re-looking at Netlify CMS yesterday (
https://www.netlifycms.org/ )  I initially looked at it a couple of years
ago for my old company when we needed some client editing options for
static sites, but it wasn't really ready then.  Might offer a better UI for
wiki-like functionality, possibly even with the JBake main site.  Shows we
have options if nothing else.

Best wishes,

Neil
-- 
Neil C Smith
Artist & Technologist
www.neilcsmith.net

Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org

Re: Ready to vote on Apache NetBeans (incubating) 9.0 Beta RC3?

2018-01-27 Thread Geertjan Wielenga 
Nice, thanks a lot!

Gj

On Sat, Jan 27, 2018 at 2:59 PM, Matthias Bläsing
 wrote:
> Hey,
>
> please wait - I'm preparing a change to the way license and notice are
> generated and I think that should go in before another vote.
>
> I'll try to get a prototype out this weekend.
>
> Matthias
>
> Am Samstag, den 27.01.2018, 14:54 +0100 schrieb Geertjan Wielenga:
>> Hi all,
>>
>> It seems to me that the main items identified by the IPMC vote have
>> been addressed:
>>
>> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+
>> 9.0+Beta+rc3
>>
>> And thanks to Eric Barboni we now have a separate and well structured
>> Rat exclusions file, which should make reviews easier:
>>
>> https://github.com/apache/incubator-netbeans/blob/master/nbbuild/rat-
>> exclusions.txt
>>
>> The file above is also referenced in our README:
>>
>> https://github.com/apache/incubator-netbeans/blob/master/README.md
>>
>> The above file is also the README that is bundled as the README of
>> the
>> source distribution.
>>
>> Take note also of our mentor Bertrand's observation -- "there are
>> many
>> exclusions" is not a release blocking problem for a podling release
>> IMO, as long as there's a plan to fix that.
>>
>> Clearly we have listed all the issues identified by Justin, see the
>> first link above.
>>
>> So, should we go ahead with a new VOTE thread for the PPMC at this
>> point or is there anything that still needs to be resolve?
>>
>> Thanks,
>>
>> Gj
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
>> For additional commands, e-mail: dev-help@netbeans.incubator.apache.o
>> rg
>>
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>
>>
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Ready to vote on Apache NetBeans (incubating) 9.0 Beta RC3?

2018-01-27 Thread Geertjan Wielenga 
Hi all,

It seems to me that the main items identified by the IPMC vote have
been addressed:

https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+9.0+Beta+rc3

And thanks to Eric Barboni we now have a separate and well structured
Rat exclusions file, which should make reviews easier:

https://github.com/apache/incubator-netbeans/blob/master/nbbuild/rat-exclusions.txt

The file above is also referenced in our README:

https://github.com/apache/incubator-netbeans/blob/master/README.md

The above file is also the README that is bundled as the README of the
source distribution.

Take note also of our mentor Bertrand's observation -- "there are many
exclusions" is not a release blocking problem for a podling release
IMO, as long as there's a plan to fix that.

Clearly we have listed all the issues identified by Justin, see the
first link above.

So, should we go ahead with a new VOTE thread for the PPMC at this
point or is there anything that still needs to be resolve?

Thanks,

Gj

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans 9.0 Beta (incubating) rc2

2018-01-27 Thread Geertjan Wielenga 
On Mon, Jan 22, 2018 at 11:44 AM, Bertrand Delacretaz
 wrote:
> On Mon, Jan 22, 2018 at 11:26 AM, Geertjan Wielenga
>  wrote:
>> I think we need a Wiki that lists all the items in Justin’s mail, each with
>> a separate row in a table, each pointing to an issue in Apache NetBeans
>> Issuezilla...
>
> Listing problems mentioned here is good indeed and JIRA is a good
> place to track them.
>
> About "what do NetBeans mentors think", given the vast number of files
> in the NetBeans release, we mentors have suggested early on that a RAT
> exclusion lists be created, with comments which indicate why each
> extension is here.

Here is that file:

https://github.com/apache/incubator-netbeans/blob/master/nbbuild/rat-exclusions.txt

Do you or anyone else have comments on it?

> When reviewing this release, I had a look at the (many) RAT exclusions
> and didn't spot anything problematic but maybe I missed something - if
> someone can point to specific exclusions which are not acceptable at
> [1] that's useful.
>
> Apart from that, "there are many exclusions" is not a release blocking
> problem for a podling release IMO, as long as there's a plan to fix
> that.


The above is good to read, thanks.

Geertjan



>
> -Bertrand
>
> [1] 
> https://github.com/apache/incubator-netbeans/blob/master/nbbuild/build.xml#L2077
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

AW: Improve Git Support

2018-01-27 Thread Christian Lenz 
Great Thing Jaroslav. Of Course we need more and better git support in 
NetBeans, like the long asked feature for a visual git log like this: 
https://blog.jetbrains.com/idea/files/2011/11/log1.jpg. Only to let you know 
that. This is of Course another topic and I will create a new ticket for this. 
I did it in the bugzilla board already.


Cheers and great work

Chris

Von: Jaroslav Tulach
Gesendet: Samstag, 27. Januar 2018 10:00
An: Apache NetBeans
Betreff: Improve Git Support

Hi devs,
if you want to get familiar with (part of) NetBeans code base and contribute 
to development of this IDE, here is a quest:

Please take a look at my PR: https://github.com/apache/incubator-netbeans/
pull/391/files

It improves the "Show Git History" window to handle `git replace`. It is a 
simple change - when there is no parent of certain Git RevCommit - search 
refs/replace/ and continue the search from there.

Don't you want to improve your development karma by doing the same for "Show 
Annotations" e.g. `git blame` support?

-jt

PS: In any case I need a reviewer to approve my change, so give me a +1, 
please.

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Improve Git Support

2018-01-27 Thread Jaroslav Tulach 
Hi devs,
if you want to get familiar with (part of) NetBeans code base and contribute 
to development of this IDE, here is a quest:

Please take a look at my PR: https://github.com/apache/incubator-netbeans/
pull/391/files

It improves the "Show Git History" window to handle `git replace`. It is a 
simple change - when there is no parent of certain Git RevCommit - search 
refs/replace/ and continue the search from there.

Don't you want to improve your development karma by doing the same for "Show 
Annotations" e.g. `git blame` support?

-jt

PS: In any case I need a reviewer to approve my change, so give me a +1, 
please.

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: info requested regarding build fail

2018-01-27 Thread Emilian Bold 
Would be nice to also see this bug reported to SUSE so we can reference it in 
the future.

​--emi


 Original Message 
 On 21 January 2018 1:44 PM, Markus Kilås  
wrote:

>On 01/20/2018 07:10 PM, Neil C Smith wrote:
>>On Sat, 20 Jan 2018, 17:54 Glenn Holmer, ce...@kolabnow.com wrote:
>>>Is it possible that SUSE installs Ant with a dependency of OpenJDK and
>>> uses that when it's run? Could that make a difference?
>>>Considering those of us building and testing on OpenJDK seem to be in the
>> majority, I doubt it.
>>I'm actually currently building with the Ubuntu packaged Ant 1.9.3 (problem
>> Ant is only 1.9.8 AFAIK). All works fine. Sounds like Suse might have a
>> packaging issue?
>>^^ isn't meant as recommended - pure laziness on my part - still, while
>> it's working... ;-)
>>Best wishes,
>>Neil
>>>--
>>> Neil C Smith
>>> Artist & Technologist
>>>www.neilcsmith.net
>>>Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
>>
>
> I reported the same build failure also with Fedora 26 and its packaged
> Ant 1.10.1. See here for the 4 different environments I tried:
>https://issues.apache.org/jira/browse/NETBEANS-239
>
> The conclusion is that in those environments where the NetBeans build
> script is not compatible with the distribution's version of Ant (or
> wise-versa if you like), you can instead download the Apache Ant binary
> dist and use that, i.e.:
> export ANT_HOME=/opt/my-apache-ant-dist
> export PATH=$ANT_HOME/bin:$PATH
>
> Also as pointed out make sure to use a fresh clone and don't relay on
> the clean target.
>
>
> Cheers,
> Markus
>
>
>
>
>To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
>https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [Plugins] How to open archive files by MIME type?

2018-01-27 Thread Emilian Bold 
>There is no plan to release the sources since you can do this with the build 
>in "New File Type"-Wizard on your own.

How can this be closed source when the licenses is listed as Apache 2.0 here 
http://plugins.netbeans.org/plugin/55342/office-file-types?

--emi
​

 Original Message 
 On 24 January 2018 10:30 AM, Jens Hofschröer  wrote:

>Hi
>
> Am 22.01.2018 um 09:37 schrieb Christian Lenz:
>>There is already a plugin for those file types: 
>>http://plugins.netbeans.org/plugin/55342/office-file-types unfortunately, 
>>there is no link to the Code repo. [...] You can try to write the developer.
>>
> I am the author of this plugin (and the sources are not mine). It is
> only a collection of registered MIME-Resolver as described in [1], no
> magic. Just call Desktop.open() on the FileObject.
>
> There is no plan to release the sources since you can do this with the
> build in "New File Type"-Wizard on your own.
>
> Greetings
> Jens
>
> [1] https://platform.netbeans.org/tutorials/nbm-filetype.html
>
>
>>Von: Peter Nabbefeld
>> Gesendet: Montag, 22. Januar 2018 00:40
>> An: dev@netbeans.incubator.apache.org
>> Betreff: [Plugins] How to open archive files by MIME type?
>>Hello,
>>it seems impossible to open files from LibreOffice, MS Office etc. with
>> NetBeans, as they're detected as archives, and special handling is assigned.
>>How can I open such files using DataLoaders?
>>Kind regards
>> Peter
>>
>>To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
>> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>>For further information about the NetBeans mailing lists, visit:
>>https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>
>
>
>
>http://blog.nigjo.de/netbeans/
>
>
>To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
>https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: ***UNCHECKED*** github wiki experiment

2018-01-27 Thread Emilian Bold 
This is pretty great.
​
--emi


 Original Message 
 On 26 January 2018 6:47 PM, Antonio  wrote:

>Hi all,
>
> As an experiment I've uploaded the NetBeans DevFaq wiki entries to
>
>https://github.com/vieiro/incubator-netbeans-website/wiki
>
> Which is associated with the git repo
>
>https://github.com/vieiro/incubator-netbeans-website.wiki.git
>
> The idea is to experiment with this to see if it fits our needs. Please
> add or modify entries as you see fit. Do not worry about content, as it
> will be wiped out later.
>
> Things to experiment with:
> - See how pages can be modified by the team. The wiki is unrestricted
> right now (I think) but maybe we want to restrict modifications to
> collaborators [1].
>
> - See if the github editor is good enough for us.
>
> - AFAIK github's wikis do not support PRs. Approving content may be an
> issue.
>
> If it does not fit our needs we may want to experiment with other
> alternatives:
>
>
> - Store the wiki in a plain github repo (not a wiki one), and use the
> 'gh-pages' to render it to html in github.
>
> - Store the wiki in a plain github repo and use the static site
> generator to publish it somewhere else.
>
> - Use Apache's MoinMoin to render and edit the wiki.
>
> - Any others you may think of.
>
> So please give it a run and complain as appropriate.
>
> Thanks,
> Antonio
>
>
> [1]
>https://help.github.com/articles/changing-access-permissions-for-wikis/
>
>
>To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
>https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists