src/site/** ? What exactly are you wanting to generate a readme from? Certainly not everything under src/site.
Ralph > On Apr 26, 2016, at 2:27 AM, Mikael Ståldal <mikael.stal...@magine.com> wrote: > > Would it be possible to generate README.md from src/site/** ? > > On Mon, Apr 25, 2016 at 6:55 PM, Matt Sicker <boa...@gmail.com > <mailto:boa...@gmail.com>> wrote: > I noticed that after I sent the first email ;) > > We can probably include info from the wiki, FAQ, or some other site manual > pages. > > On 25 April 2016 at 11:12, Mikael Ståldal <mikael.stal...@magine.com > <mailto:mikael.stal...@magine.com>> wrote: > I just added a README.md file as a starting point. We might want to add > information about how to fetch it. > > On Mon, Apr 25, 2016 at 5:57 PM, Mikael Ståldal <mikael.stal...@magine.com > <mailto:mikael.stal...@magine.com>> wrote: > We need a public GitHub repository with: > - a README.md file in Markdown format (as usual on GitHub) which describes > where to download and how to use the it > - a LICENSE or COPYING file with the license (our current LICENSE.txt will do) > > Read more here: http://docs.graylog.org/en/latest/pages/marketplace.html > <http://docs.graylog.org/en/latest/pages/marketplace.html> > > > On Sun, Apr 24, 2016 at 4:07 AM, Remko Popma <remko.po...@gmail.com > <mailto:remko.po...@gmail.com>> wrote: > Mikael, can you prepare or list up what needs to be done for the GelfLayout > to be listed on the graylog marketplace site? Does the README need to be > GelfLayout-specific or does it need to be about log4j2 in general? I don't > have time to investigate... > > Sent from my iPhone > > On 2016/04/24, at 4:57, Matt Sicker <boa...@gmail.com > <mailto:boa...@gmail.com>> wrote: > >> That's not even the right GitHub repository. Here: >> https://github.com/apache/logging-log4j2 >> <https://github.com/apache/logging-log4j2> >> >> On 18 April 2016 at 10:05, Mikael Ståldal <mikael.stal...@magine.com >> <mailto:mikael.stal...@magine.com>> wrote: >> You need proper permissions to the Apache organization on GitHub, which I >> don't seem to have. >> >> We can use the existing repository https://github.com/apache/log4j >> <https://github.com/apache/log4j> >> >> Is probably a good idea to have a README.md in that repository anyway, it is >> good practice on GitHub. >> >> On Mon, Apr 18, 2016 at 4:55 PM, Remko Popma <remko.po...@gmail.com >> <mailto:remko.po...@gmail.com>> wrote: >> Mikael, >> >> Looks like this needs at least a README and a release. Should we do this >> when we release 2.6 then? Someone needs to prepare the README. >> >> Also, what kind of GitHub permissions would be required? >> >> Remko >> >> >> On Mon, Apr 18, 2016 at 11:49 PM, Mikael Ståldal <mikael.stal...@magine.com >> <mailto:mikael.stal...@magine.com>> wrote: >> Perhaps someone from PMC should register Log4j 2 here: >> http://docs.graylog.org/en/latest/pages/marketplace.html >> <http://docs.graylog.org/en/latest/pages/marketplace.html> >> >> now when we have a GelfLayout. >> >> Currently you will only find a couple of obsolete third-party GELF-plugins >> for Log4j. >> >> I tried to do it myself, but I don't have the proper permissions on GitHub. >> >> -- >> >> >> Mikael Ståldal >> Senior software developer >> >> Magine TV >> mikael.stal...@magine.com <mailto:mikael.stal...@magine.com> >> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com >> <http://www.magine.com/> >> >> Privileged and/or Confidential Information may be contained in this message. >> If you are not the addressee indicated in this message >> (or responsible for delivery of the message to such a person), you may not >> copy or deliver this message to anyone. In such case, >> you should destroy this message and kindly notify the sender by reply email. >> >> >> >> >> >> -- >> >> >> Mikael Ståldal >> Senior software developer >> >> Magine TV >> mikael.stal...@magine.com <mailto:mikael.stal...@magine.com> >> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com >> <http://www.magine.com/> >> >> Privileged and/or Confidential Information may be contained in this message. >> If you are not the addressee indicated in this message >> (or responsible for delivery of the message to such a person), you may not >> copy or deliver this message to anyone. In such case, >> you should destroy this message and kindly notify the sender by reply email. >> >> >> >> >> -- >> Matt Sicker <boa...@gmail.com <mailto:boa...@gmail.com>> > > > > -- > > > Mikael Ståldal > Senior software developer > > Magine TV > mikael.stal...@magine.com <mailto:mikael.stal...@magine.com> > Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com > <http://www.magine.com/> > > Privileged and/or Confidential Information may be contained in this message. > If you are not the addressee indicated in this message > (or responsible for delivery of the message to such a person), you may not > copy or deliver this message to anyone. In such case, > you should destroy this message and kindly notify the sender by reply email. > > > > > -- > > > Mikael Ståldal > Senior software developer > > Magine TV > mikael.stal...@magine.com <mailto:mikael.stal...@magine.com> > Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com > <http://www.magine.com/> > > Privileged and/or Confidential Information may be contained in this message. > If you are not the addressee indicated in this message > (or responsible for delivery of the message to such a person), you may not > copy or deliver this message to anyone. In such case, > you should destroy this message and kindly notify the sender by reply email. > > > > > -- > Matt Sicker <boa...@gmail.com <mailto:boa...@gmail.com>> > > > > -- > > > Mikael Ståldal > Senior software developer > > Magine TV > mikael.stal...@magine.com <mailto:mikael.stal...@magine.com> > Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com > <http://www.magine.com/> > > Privileged and/or Confidential Information may be contained in this message. > If you are not the addressee indicated in this message > (or responsible for delivery of the message to such a person), you may not > copy or deliver this message to anyone. In such case, > you should destroy this message and kindly notify the sender by reply email. >
