[Free-RTC Discuss] Awesome RTC

Ciprian Dosoftei ciprian.dosoftei at gmail.com
Fri Feb 7 00:16:23 GMT 2020


After mulling it over, I think a more structured data format is better
suited.

For example, a YAML file -- no love lust with the format, it just plays
nicer with source control tools -- could be the primary source, then during
CI, it can be transformed into other deliverables (JSON, CSV, XML etc).

Here's a proof of concept I put together:

https://github.com/cdosoftei/awesome-rtc/blob/master/meta.yaml

And here's a simple browser based JS consumer:
https://rtckit.io/os-rtc-index/

I've deliberately left out the events portion; after a cursory check, not
all event websites expose an iCal feed. I am thinking these could be
structured entries for each project; during CI, iCal files could be
generated and/or consumers can create their own artifacts.

Any thoughts? Thanks!

On Thu, 6 Feb 2020 at 15:04, Ciprian Dosoftei <ciprian.dosoftei at gmail.com>
wrote:

> Hi Daniel --
>
> Maintainer of rtckit/awesome-rtc <https://github.com/rtckit/awesome-rtc>
> here; I like the RSS feed idea, that's something I could wire up in the
> repository's CI routine.
>
> It should be more effective than GitHub's notifications ... at least in my
> personal case, I've grown a bit numb to them (difficult to keep up with).
>
> -Ciprian
>
> On Thu, 6 Feb 2020 at 14:41, Daniel Pocock <daniel at pocock.pro> wrote:
>
>>
>>
>> On 03/02/2020 08:15, Saúl Ibarra Corretgé wrote:
>> > This has already been done a couple of times, it was brought to my
>> > attention
>> > yesterday: https://twitter.com/saghul/status/1223908763981185024?s=21
>> >
>> > I see no reason to duplicate efforts here. We could just contribute to
>> > them and link them appropriately.
>> >
>>
>>
>> https://github.com/QXIP/awesome-voip-rtc
>> https://github.com/rtckit/awesome-rtc
>>
>>
>> Could we gather this data in a CSV file, table or JSON somehow?
>>
>> It would be really useful to have a collection of links for each
>> project, especially:
>>
>> RSS / Atom feed
>> iCalendar event feed
>>   (with both events as VEVENT and CFP deadlines as VTODO)
>> bug tracker URL
>> Git URL
>> mailing list URL
>> a list of tags per-project, e.g. sip, xmpp, webrtc
>> logo URL
>>
>> People could then make their own scripts to consume the table, monitor
>> the iCalendar or RSS feeds or whatever they want to do.
>>
>> Would anybody like to suggest a tool to maintain something like this or
>> a CSV file in Git is sufficient?
>> _______________________________________________
>> Discuss mailing list
>> Discuss at lists.freertc.org
>> http://lists.freertc.org/mailman/listinfo/discuss
>>
>
>
> --
> Best Regards,
> Ciprian Dosoftei
>
> The information transmitted is intended only for the addressee and may
> contain privileged and/or confidential material. If you are not the
> intended recipient, kindly contact the sender and delete the message.
>
> Any disclosure, distribution or copying of this message is strictly
> prohibited without the expressed permission of the sender.
>


-- 
Best Regards,
Ciprian Dosoftei

The information transmitted is intended only for the addressee and may
contain privileged and/or confidential material. If you are not the
intended recipient, kindly contact the sender and delete the message.

Any disclosure, distribution or copying of this message is strictly
prohibited without the expressed permission of the sender.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freertc.org/pipermail/discuss/attachments/20200206/3b9704af/attachment-0001.htm>


More information about the Discuss mailing list