Hi @Shachar Itzhaky @Hanneli Tavante
I'm moving the discussion here as the hacktahon is over; so indeed we finally didn't have time to meet last week, but we discussed about doing a half a day event in the next weeks, focused solely in jsCoq hacking
The hackathon was too disperse and with too many topics as to be effective it seems
I know a few people that would be interested in joining such an event
Ok I am in favor yeah. I feel some remorse for not having participated in the hackathon at all, I agree it is too erratic when most people are not in Paris.
+1 I'm happy to participate in a focused working day for jsCoq :)
I would be happy if we can (1) Come up with some kind of Quick Start guide to help newcomers run their own version of jsCoq even if they are not familiar with Node/NPM, (2) Refactor the jsCoq landing page a little bit. Esp. I think that we should also have a simpler example and maybe one that does not use ssreflect (sorry @Emilio Jesús Gallego Arias) as to be accessible to a wider audience.
So maybe we can open the wiki page (@Hanneli Tavante you did that already right) and add our topics
I have quite a few, will ping the students that wrote to me by mail
Indeed the dev workflow can be improved a lot, we also face a few challenges w.r.t. maintenance which I will try to detail
and the event would be great to actually for all of us to meet and discuss a bit about the platforms and the chanllenges
going back to the topic of this thread, I suggest we ping informally most people interested, fill the wiki page
and try to open the scheudling pool for end of the week
Emilio Jesús Gallego Arias said:
So maybe we can open the wiki page (Hanneli Tavante you did that already right) and add our topics
https://github.com/coq/coq/wiki/jsCoq--and-CoqDB-Working-Day
Thanks @Hanneli Tavante
What is the best way to set a date for the event?
What do you think of making an announcement first, and having a doodle on it?
Sounds good; where do you plan to announce it?
@Hanneli Tavante I think we could use discuss and coq-club, what do you think?
I am very busy until March 1st as I need to submit my tenure paperwork, bear with me not being very responsive
but once I do that I have plenty of time
discuss
Note that Discuss is Discourse. It's an OCaml-thing that it is called Discuss.
Sure, let's work on it when you have time after Mar 1st. Good luck @Emilio Jesús Gallego Arias !
Ok folks, I am free of full-time grant writing, so I think we can start to think of setting up a date and preliminary program
Should we use a poll for the date?
Should we announce the poll in the usual places?
By usual places do you mean here at Zulip + mailing list + Twitter?
Yes, I think so, also discourse
We need to tweak the wiki page a bit first I guess, but we can take as a model the announcement for the Hackathon
Hanneli I think I'd be great if you would like to take the lead on the announcements, for Twitter just tag @coqlang and we'll retweet
Cool, I'll send a draft message here in a few hours; if it looks good I'll go ahead and send it
Ideally we'll need to suggest dates+times where you are also available @Emilio Jesús Gallego Arias. Do you have any preference? If not, I'll go for end of March + Early April afternoon time Central Europe
@Hanneli Tavante that timeline suits me very well
I don't have anything important
Message draft
==========
Hi everyone,
The previous Coq Hackathon and workgroup, held on Feb 15th-17th 2022, was great, and we plan to have an extra half-day day session to cover jsCoq and CoqDB.
We will add the session details in this dedicated page. At this time, we would like to define the date for this upcoming event. Please edit the When
section in the Wiki and add your name after the options that are most convenient for you.
We are looking forward to seeing you in our next work session! If you have any questions, do not hesitate to ask them in our Zulip
\cc @Emilio Jesús Gallego Arias ^
Thanks @Hanneli Tavante , how about actually doing a doodle instead of the wiki?
The draft looks good to me, find a pass here (feel free to take my edits or not, they are just suggestions)
A problem we have is that "CoqDB" doesn't exist yet, so I'll try to explain what it is, hence a bit of more deep reword than I usually do.
========
Hi everyone,
we happy to announce a half-day jsCoq hacking event. The format is inspired by the previous Coq Hackaton which we think worked great.
A particular topic of interest we aim to discuss, and not directly related to jsCoq is the topic of building a "CoqDB", an attempt to develop a unified framework where information about Coq objects and metadata can be handled.
Please fill the planning poll with the dates that would work best for you, and the wiki page to add your own suggestions / ideas / requests.
We are looking forward to seeing you in this event! If you have any questions, do not hesitate to ask them in our Zulip
@Emilio Jesús Gallego Arias
==================
Hi everyone,
The previous Coq Hackathon and workgroup, held on Feb 15th-17th 2022, was great, and we plan to have an extra half-day session.
You can find more details on our dedicated page. At this time, we would like to define the date for this upcoming event. Please use this Doodle to select the option(s) that is (are) most convenient for you.
In this upcoming session, we plan to work on two topics: jsCoq (see the Wiki section here) and the initial implementation of "CoqDB", an attempt to develop a unified framework where information about Coq objects and metadata can be handled (see the Wiki section here).
We are looking forward to seeing you in our next work session! If you have any questions, do not hesitate to ask them at Zulip
@Hanneli Tavante looks good thanks, tho I'd maybe rephrase the starting sentence
IMHO we should start with the goal of the message: "we are happy to announce X"
to praise the previous workshop seems a bit secondary to me
in terms of people understanding what the message is about
actually I also think that "an extra half-day session" is too vague, this is mainly a jscoq event I think
we could say as you did jscoq + coqdb
but we have the problem that coqdb nobody knows what it is
==========
Hi everyone,
We are organizing an upcoming Coq Hackathon and workgroup session to work on two topics: jsCoq (see the Wiki section here) and the initial implementation of "CoqDB", an attempt to develop a unified framework where information about Coq objects and metadata can be handled (see the Wiki section here).
At this time, we would like to define the date for this upcoming event. Please use this Doodle to select the option(s) that is (are) most convenient for you.
We are looking forward to seeing you in our next work session! If you have any questions, do not hesitate to ask them at Zulip
^ if this looks goo, I'll send it out on Mon @Emilio Jesús Gallego Arias
Looks very good to me thanks!
Cool, announcements sent at the mailing list, discourse and Twitter! (\cc @Emilio Jesús Gallego Arias && @Evariste G )
Thanks @Hanneli Tavante , twitter is done, should we also add https://coq.discourse.group/ ?
I can take of if if you are busy.
I sent a message earlier on, but I think it's held for moderation (apparently)
[Edit: Ah yes, the user account is on hold :sweat_smile:]
Oh! Let me look into that
thanks!
Hanneli Tavante said:
thanks!
Thanks to you!
@Shachar Itzhaky We are planning an upcoming session to work on jsCoq, and I see you were mentioned in previous threads about it. Do you think you could make it to one of these timeslots? https://doodle.com/meeting/participate/id/lejjXAWe
thanks @Hanneli Tavante , I cannot quite fit the entire 3 hours into my schedule but I may be able to attend a part of the time. I can do most of the Thu 3-6p so I'll mark that, if you choose the others I might join for ~1hr.
Thanks! I think we can make this work :)
Hello, is there some connection information somewhere?
Yes! @Yves Bertot Zoom link
Session starting shortly here
Hi folks, we have tweked the program a bit.
Please have a look at the wiki page
https://github.com/coq/coq/wiki/jsCoq--and-CoqDB-Working-Day
we will be starting the 5:10pm session at 5pm instead
Last updated: May 31 2023 at 02:31 UTC