Hi there. Some words to tell you that the documentation effort start taking shape. A savannah project has been created in order to coordinate work: http://savannah.nongnu.org/projects/interopcast/ CVS is accessible via cvsweb here: http://savannah.nongnu.org/cgi-bin/viewcvs/interopcast/ A first html shot available for browsing here: (there are other documents to merge with but not yet http available, to be coming) http://melmoth.dyndns.org/stream/doc/ Interopcast will participate in documentation effort and in developpment as one of its member is working in a computer school and is using icecast enhancement as a student project (8 students will be working on it). More news about this student work in some days. Now for the documentation questions. As several people have already began writing usefull documents about icecast 1 or 2, we are trying to merge works in order to create a single document that may end as an 'official' documentation. Archives of mail about how this is going may be readable here: http://mail.gnu.org/archive/html/interopcast-general/ Several questions have been asked and i'm sure icecast's developper may have good ideas about what is to be done. What's the average technical knowledge level of intended audience that shall be presume for such a document ? As i would be pleased to have several translations of the document, i would like to have this document the most icecast specific as possible (less translation work :) ). Documentation format is now docbook, but a man compatible version would also be interesting to have. Anybody knows if docbook2pod is something easily done ? How many document to create ? A proposed idea would be to have 3 differents ones: - a general icecast presentation, sort of marketing like without technical stuff targeted at non technician taking decision about what software to use in their streaming project. - a technical presentation targeted at administrator that have to install icecast and developper that intend to customize it. - an exploitation document target at technician that have to use the software in production. <p>I guess a good way of starting would be to agree on the number of document to create, the table of contents for each one. Then we would be able to divise work, share it amongst volounteer and once a correct english version would be available start translating in several language and man format. Any ideas, suggestions ? Have a nice day. Pierre Amadio <p><p><p>--- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
><snip> > Several questions have been asked and i'm sure icecast's developper may > have good ideas about what is to be done. > > What's the average technical knowledge level of intended audience that > shall be presume for such a document ?Oops. Sorry for the late response - I missed this at first for some reason. I think this should be aimed at a technical but not expert audience, for the most part. i.e. people who are competent with computers, and have some idea that the internet IS more than just the web, but don't know much about internet radio. <p>>> As i would be pleased to have several translations of the document, i > would like to have this document the most icecast specific as possible > (less translation work :) ). > > Documentation format is now docbook, but a man compatible version would > also be interesting to have. Anybody knows if docbook2pod is something > easily done ?I have a docbook-to-man installed on my system (never used it, though). Not sure about pod, but I don't see why you'd want it.> > How many document to create ? A proposed idea would be to have 3 > differents ones: > > - a general icecast presentation, sort of marketing like without > technical stuff targeted at non technician taking decision about what > software to use in their streaming project.This sounds like a useful one that I hadn't thought of.> > - a technical presentation targeted at administrator that have to > install icecast and developper that intend to customize it. > > - an exploitation document target at technician that have to use the > software in production.I'm not sure what you mean by 'exploitation' here, and it's not entirely clear to me what should NOT go into a technical/admin doc that would be left over for a 3rd document. Can you clarify?> > > I guess a good way of starting would be to agree on the number of > document to create, the table of contents for each one. Then we would be > able to divise work, share it amongst volounteer and once a correct > english version would be available start translating in several language > and man format.Sounds pretty good.> > Any ideas, suggestions ? > > Have a nice day. > > Pierre AmadioMike --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
Hi there.> > also be interesting to have. Anybody knows if docbook2pod is something > > easily done ? > > I have a docbook-to-man installed on my system (never used it, though). Not > sure about pod, but I don't see why you'd want it.Is not pod the man format ? Did i mean docbook2groff ? :) I saw this docbook2man script but it generate error if i try to use it with my doc or kerry's one. I intent to look at how docbook-xml and xsltproc works before adding more content or merging stuff as a friend told me it may be a better way to generate docbook output than jade scripts. Next goal for me: having a Makefile that generate doc in wanted format with xslt-proc. Hope i wont be too slow on this.> I'm not sure what you mean by 'exploitation' here, and it's not entirely clear > to me what should NOT go into a technical/admin doc that would be left over > for a 3rd document. Can you clarify?I don't know the english for 'production'. Usually production technician are not so skilled tekies in prod environnemnt having process to check and a documentation to follow such as 'if this led start being red, enter this command and dial 911'. I guess it would be something like a 'what to do if this problem arise' in a 'copy and paste' command format. Not sure although that that was the way it was meant to be by the guy who proposed the 3 different documents. Here how i see the 3 document: the 3 part of the doc i was starting to wrote. 1) A picture of tools -> marketting stuff (lots of buzz word to be added :) ) 2) Installing sofwtare Configuring software -> unix admin targetted audience. 3) Streaming sound on the internet: production doc. I merged this doc with Ciaran Anscomb's Ices2 Howto yesterday, and just imported kerry's howto in savannah's cvs few minutes ago. Things i would like to see added: -3rd application sofwtare notes: darkices : compile,configure and run. other streamer i havent yet heard of but who are nices. streaming and admin connection over ssl (yeaah, i really think it s an important issue) as in http://melmoth.dyndns.org/stream/ssl/index.html Have a nice day. Pierre Amadio <p><p><p><p>>> > > > > > I guess a good way of starting would be to agree on the number of > > document to create, the table of contents for each one. Then we would be > > able to divise work, share it amongst volounteer and once a correct > > english version would be available start translating in several language > > and man format. > > Sounds pretty good. > > > > > Any ideas, suggestions ? > > > > Have a nice day. > > > > Pierre Amadio > > Mike > > --- >8 ---- > List archives: http://www.xiph.org/archives/ > icecast project homepage: http://www.icecast.org/ > To unsubscribe from this list, send a message to 'icecast-dev-request@xiph.org' > containing only the word 'unsubscribe' in the body. No subject is needed. > Unsubscribe messages sent to the list will be ignored/filtered.--- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
hello, mp3src ==> icecast ==> clients * as shown above, when rebroadcasting streams from mp3 source, how can i write code on the server to locate song boundaries? i would like to keep track of songs that are broadcasted, number of people listening to it etc. thanks, deva <p><p>--- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.