On January 13, 2014 04:12:29 PM Florian Jung wrote: > Am 09.01.2014 00:31, schrieb Tim E. Real: > > Nah, I found a suitable solution: > > > > I moved all the files back into /muse2, and added > > > > a top-level file README.md > > > > README.md is a special 'markdown' (html) file > > > > which is the 'front face' of the project, an alternative > > to the plain README file. > > > > This file can contain LINKS to all the other (README) files. > > Anything we want. > > We just need to make it look nice, but simple. > > In other words, a nice html intro to MusE. > > Take a look at it, I just have the word 'TESTING' in there now. > > Hi Tim, > > could you please fill the README.md with content ASAP, it would really > rock to have a description of why muse is cool on the main page of github. > > I'll merge it into my repo, then. > > Cheers, > flo
Done. Just one problem: The two MusE releases found in the github repo are too old (2.0). I could not figure out how to transfer files (SourceForge release_x.tar.gz) into the github muse/releases folder. Can someone please do it? Please do *not* construct a new release from git master yet. There are some issues to be resolved. Because of this, in README.md I pointed my 'current releases' link to the SourceForge downloads page, where 2.1.2 can be found. Thanks. Tim. ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
