4 Apr
2016
4 Apr
'16
4:51 a.m.
Hi Markus,
nice!
Maybe, the
EBU-Meter can added to this list.
http://kokkinizita.linuxaudio.org/linuxaudio/ebumeter-doc/quickguide.html
done!
I'll collect more changes before creating the next
pull request.
I've written a full radio automation that also uses jack. Unfortunately
the docs are incomplete..
https://github.com/srb-fm/admin-srb
https://plus.google.com/+JoergSorge/posts/8KiCZ4194Aj
Regards, Jörg
4 Apr
4 Apr
12:41 p.m.
New subject: [Jack-Devel] jackaudio.org pull request
On 04/04/2016 11:50 AM, JoergSorge wrote:
Hi Markus,
nice!
Do you think the software is in a state such that end users can build,
install, configure and use it themselves?
Maybe,
the EBU-Meter can added to this list.
http://kokkinizita.linuxaudio.org/linuxaudio/ebumeter-doc/quickguide.html
done!
I'll collect more changes before creating the
next pull request.
I've written a full radio automation that also uses jack. Unfortunately
the docs are incomplete..
https://github.com/srb-fm/admin-srb
https://plus.google.com/+JoergSorge/posts/8KiCZ4194Aj
Regards, Jörg
5 Apr
5 Apr
8:38 a.m.
New subject: [Jack-Devel] jackaudio.org pull request
Do you think the software is in a state such that end
users can build,
install, configure and use it themselves?
That's a good question ;-) I know, I have a lot to do to make install
and docs user friendly...
Regards Jörg
6 Apr
6 Apr
11:38 a.m.
New subject: [Jack-Devel] jackaudio.org pull request
On 04/05/2016 03:38 PM, JoergSorge wrote:
I tracked your request anyway:
https://github.com/jackaudio/jackaudio.github.com/issues/45
If you think it is worth sharing, I'll include it.
Best regards
Markus
Do you think the software is in a state such that
end users can build,
install, configure and use it themselves?
That's a good question ;-) I know, I have a lot to do to make install
and docs user friendly...
Regards Jörg
3 May
3 May
1:05 p.m.
New subject: [Jack-Devel] jackaudio.org pull request
Markus - pulled the site, but the contents of the _site folder/dir do not
appear up to date ...
On Wed, Apr 6, 2016 at 12:38 PM, Markus Seeber <
markus.seeber(a)spectralbird.de> wrote:
On 04/05/2016 03:38 PM, JoergSorge wrote:
I tracked your request anyway:
https://github.com/jackaudio/jackaudio.github.com/issues/45
If you think it is worth sharing, I'll include it.
Best regards
Markus
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Do you think the software is in a state such that
end users can build,
install, configure and use it themselves?
That's a good question ;-) I know, I have a lot to do to make install
and docs user friendly...
Regards Jörg
1:38 p.m.
New subject: [Jack-Devel] jackaudio.org pull request
This is correct. It is in sync with the changes I mentioned with the
last "pull request mail". The reason for not rebuilding "_site" on
every
commit is, that changes to markdown files may generate a lot of changes
in "_site" so I do not commit "_site" on every change.
I can create tags in future to signal a release, would this be appropriate?
On 05/03/2016 08:05 PM, Paul Davis wrote:
Markus - pulled the site, but the contents of the
_site folder/dir do not
appear up to date ...
On Wed, Apr 6, 2016 at 12:38 PM, Markus Seeber <
markus.seeber(a)spectralbird.de> wrote:
> On 04/05/2016 03:38 PM, JoergSorge wrote:
>>> Do you think the software is in a state such that end users can build,
>>> install, configure and use it themselves?
>> That's a good question ;-) I know, I have a lot to do to make install
>> and docs user friendly...
>> Regards Jörg
>>
> I tracked your request anyway:
> https://github.com/jackaudio/jackaudio.github.com/issues/45
>
> If you think it is worth sharing, I'll include it.
>
> Best regards
> Markus
> _______________________________________________
> Jack-Devel mailing list
> Jack-Devel(a)lists.jackaudio.org
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
>
1:48 p.m.
New subject: [Jack-Devel] jackaudio.org pull request
Well, either that or there needs to be post-pull hook that rebuilds _site
...
On Tue, May 3, 2016 at 2:37 PM, Markus Seeber <markus.seeber(a)spectralbird.de
wrote:
> This is correct. It is in sync with the changes I mentioned with the
> last "pull request mail". The reason for not rebuilding "_site"
on every
> commit is, that changes to markdown files may generate a lot of changes
> in "_site" so I do not commit "_site" on every change.
>
> I can create tags in future to signal a release, would this be appropriate?
>
> On 05/03/2016 08:05 PM, Paul Davis wrote:
> > Markus - pulled the site, but the contents of the _site folder/dir do not
> > appear up to date ...
> >
> > On Wed, Apr 6, 2016 at 12:38 PM, Markus Seeber <
> > markus.seeber(a)spectralbird.de
wrote:
> >
> >> On 04/05/2016 03:38 PM, JoergSorge wrote:
> >>>> Do you think the software is in a state such that end users can
build,
> >>>> install, configure and use it themselves?
> >>> That's a good question ;-) I know, I have a lot to do to make
install
> >>> and docs user friendly...
> >>> Regards Jörg
> >>>
> >> I tracked your request anyway:
> >> https://github.com/jackaudio/jackaudio.github.com/issues/45
> >>
> >> If you think it is worth sharing, I'll include it.
> >>
> >> Best regards
> >> Markus
> >> _______________________________________________
> >> Jack-Devel mailing list
> >> Jack-Devel(a)lists.jackaudio.org
> >> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
> >>
>
4 May
4 May
4:05 a.m.
New subject: [Jack-Devel] jackaudio.org pull request
I will think about that since that could solve some other problems too,
like being able to insert build date or commit hash or a tag into the
generated page.
Would you prefer the webserver to rebuild the page after a push? This
would require jekyll to be available on the webserver in the required
version (maintenance effort).
The other possibility would be to have discrete releases where _site is
rebuilt and tags are created, which would not require jekyll on the
webserver.
Depends on how you or anyone else maintaining the hosting would like to
have that handled.
If no decision is made, I'd rather tag discrete releases for now.
On 05/03/2016 08:48 PM, Paul Davis wrote:
Well, either that or there needs to be post-pull hook
that rebuilds _site
...
On Tue, May 3, 2016 at 2:37 PM, Markus Seeber <markus.seeber(a)spectralbird.de
> wrote:
> This is correct. It is in sync with the changes I mentioned with the
> last "pull request mail". The reason for not rebuilding "_site"
on every
> commit is, that changes to markdown files may generate a lot of changes
> in "_site" so I do not commit "_site" on every change.
>
> I can create tags in future to signal a release, would this be appropriate?
>
> On 05/03/2016 08:05 PM, Paul Davis wrote:
>> Markus - pulled the site, but the contents of the _site folder/dir do not
>> appear up to date ...
>>
>> On Wed, Apr 6, 2016 at 12:38 PM, Markus Seeber <
>> markus.seeber(a)spectralbird.de> wrote:
>>
>>> On 04/05/2016 03:38 PM, JoergSorge wrote:
>>>>> Do you think the software is in a state such that end users can
build,
>>>>> install, configure and use it themselves?
>>>> That's a good question ;-) I know, I have a lot to do to make
install
>>>> and docs user friendly...
>>>> Regards Jörg
>>>>
>>> I tracked your request anyway:
>>> https://github.com/jackaudio/jackaudio.github.com/issues/45
>>>
>>> If you think it is worth sharing, I'll include it.
>>>
>>> Best regards
>>> Markus
>>> _______________________________________________
>>> Jack-Devel mailing list
>>> Jack-Devel(a)lists.jackaudio.org
>>> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
>>>
3069
days inactive
3099
days old
jackaudio@lists.linuxaudio.org
7 comments
3 participants
participants (3)
-
JoergSorge -
Markus Seeber -
Paul Davis