These are chat archives for rdfjs/public

23rd
Apr 2018
Michael Luggen
@l00mi
Apr 23 12:51
happy to anounce the next iteration of RDF and JS http://www.zazuko.com/news
Michael Luggen
@l00mi
Apr 23 13:07
@/all we hope it is okay if we use the github.com/rdfjs/ repository for this?
BigBlueHat
@BigBlueHat
Apr 23 13:24
❤️
I did find the "press release" sent to the community channel a bit odd...though.
I realize it's been quiet in the CG for awhile, but it would've been nice for some emails to come out prior to this about the direction and to encourage more input/ideas/interest prior to a "launch" announcement
regardless, it's great to see the collaboration happening
Adrian Gschwend
@ktk
Apr 23 13:30
the non commercial partners thought the commercial one should do it, sorry about :-D
BigBlueHat
@BigBlueHat
Apr 23 13:37
:)
understand how that goes ;)
just wanted to be sure the intent was collaboration and not commerce--which is how it reads (a wee bit)
especially with the "we hope it is okay if we use the github.com/rdfjs/ repository for this?" waiting here
the group is still a group, even if it's been quiet for awhile--i.e. we should do this as a group :)
Wiley (who I represent at the W3C) is very interested this CG and this code being developed and coordinated and ideally standardized
so, +1 to doing it here (for what little my personal "vote" counts atm), but do please do it in a way that's fully collaborative, process and people oriented, with an ultimate goal of shared foundation-making
and if you need help with any of that, let me know :)
Michael Luggen
@l00mi
Apr 23 13:50
@BigBlueHat Sure as it was done up to now already. We are Open Source first!
The only big difference is that we like to work closer together.
Thomas Bergwinkl
@bergos
Apr 23 14:02
@BigBlueHat you should read it like this: "we, zazuko ruben and tim, hope it is okay if the rdfjs CG use the github.com/rdfjs/ repository for this?"
BigBlueHat
@BigBlueHat
Apr 23 14:03
gotcha. that reads better :)
it would be good to have more code happening inside CGs
are their plans to continue the spec and involve the CG members in the code collaobration (i.e. what does the CONTRIBUTING.md look like? ;) )
Thomas Bergwinkl
@bergos
Apr 23 14:05
yes, we want to finish the spec
BigBlueHat
@BigBlueHat
Apr 23 14:06
bergos: thanks again
it was mostly the silence in the group coupled with a press release (rather than a "hey CG! we'd like to consolidate our various code libraries and build them here within the CG!!1! Pull Requests Welcome!")
Michael Luggen
@l00mi
Apr 23 14:07
yes sorry, we like also to revive the group a bit
BigBlueHat
@BigBlueHat
Apr 23 14:08
great to know l00mi. thank you
Michael Luggen
@l00mi
Apr 23 14:08
so! pull request extremely welcome (-:
BigBlueHat
@BigBlueHat
Apr 23 14:09
it would be good to get new chairs elected, calls on the calendar, CONTRIBUTING.md (et al) added to the new code library space, etc.
fabulous :)
do let me know how I can help
and thanks for working together and with the wider community!
Thomas Bergwinkl
@bergos
Apr 23 14:10
i think code collaboration happend already in this CG, just not in the github organisation. but i think it was more the "core rdfjs" members. so this should be a strong signal that everyone is invited!
+1 on chairs, calls, contributing.md
Michael Luggen
@l00mi
Apr 23 14:16
contributing.md would be nice..
Sarven Capadisli
@csarven
Apr 23 14:24
I don't have much to add to here but to say that RDFa needs serious attention.
I'm mostly a user of it.. okay to QA and whatnot but not going ot get overly involved in the lower levle library stuff. You smart folks can do a better job at that based on having good familiarity with rdfjs and the direciton it should go
So... here to test/experiment with whatever you put in front of me.
Pieter Colpaert
@pietercolpaert
Apr 23 14:43
Announcement is good news, but I thought we were already collaborating ;-) Good to see we’re also now slowly going to merge organizations!
BigBlueHat
@BigBlueHat
Apr 23 19:16
pietercolpaert summed up my feelings better than I did :)
bergos l00mi perhaps one of you can follow up the earlier "press release" post with something that clarifies things for the existing community?
and maybe an initial call time vote link would also allay fears/concerns/confusions
Adrian Gschwend
@ktk
Apr 23 19:57
I’m not really sure what your fears are?
rdf-ext was always open source and probably one of the libs with the highest amount of development
payed by commercial customers of us & a lot of sparetime by @bergos
what we found pointless (and ruben and Tim) is that we develop multiple libs in parallel in a community that is already quite small
so all we are saying is that we try to align more and not duplicate work anymore
BigBlueHat
@BigBlueHat
Apr 23 21:06
ktk and put that way it's all very clear and fairly inclusively expressed :)
think the "press release" style language landing on a community mailing list was what got me concerned
BigBlueHat @BigBlueHat having been a member of several communities overtaken by other "communities"--with commercial overtake being the ultimate driver
BigBlueHat
@BigBlueHat
Apr 23 21:08
it's clear from much of the above that the intents are/were/will-be centered around collaboration--and collaboration including the existing community space
and not (as was my initial concern at least) "hi! several of us decided out-of-band what the future of this community space would be. cheers!"
given that this is in fact (thankfully!) about simply consolidating effort and includes intent to involved interested parties from beyond the other groups mentioned in the "press release"
BigBlueHat
@BigBlueHat
Apr 23 21:16
anyway. I appreciate everyone who helped clear up those concerns, and I'm excited to help make this all awesome ^_^
cheers!