Chakracore: Chakracore Future - Volunteers wanted

[rhuanjl]

As is likely obvious to anyone looking at this repository it's not very active.

There has been a hope that a community team could keep ChakraCore going BUT without some more contributors with more time it's unlikely to go far.

So - is anyone else:
a) interested in contributing to chakracore AND
b) able to actually write code

Let us know and we'll see what we can plan.

CC @ppenzin

[kmohan96214]

I have work experience of about a year and half, but really new to open source.
I'm interested. If possible include me in your plans.

[ppenzin]

@kmohan96214, we will be happy to help you get up to speed. I would also like to mention our latest contributors - @muhdmud and @unbyte.

[nli8n]

will be happy to contribute :)

[ppenzin]

@nli8n thank you for your interest, will be happy to help.

@nli8n and @kmohan96214 is there something you want to explore in the project? (it is completely OK if you don't know yet). We have tried labeling issues which would be easier to start on as "good first issue", but sometimes there can be "hidden parts to the iceberg", as @muhdmud can probably attest to :)

@rhuanjl should we organize another virtual meeting?

[rhuanjl]

@ppenzin that's a good idea - sometime next week or maybe the week after?

[ppenzin]

@rhuanjl both would work. What about everybody else?

Edit: we probably want it to schedule it before the holidays, there are only a few weeks left.

[muhdmud]

Sure, sounds good!

[ppenzin]

Let's also add @OmarMorales71 (he is interested in #6519).

[rhuanjl]

Here's a doodle poll for possible times for a meeting to discuss (the options are based on my availability - please tick any that work for you and we'll schedule a meeting at a time that works for the most people)
https://doodle.com/poll/3m9snzh2c6ui63gz?utm_source=poll&utm_medium=link

[Fly-Style]

@ppenzin @rhuanjl I had tough three months, I'll fix a bugs time to time and will implement new wasm proposals after wabbit update.

[kmohan96214]

@rhuanjl both would work. What about everybody else?

Edit: we probably want it to schedule it before the holidays, there are only a few weeks left.

Sounds good

[SumanthD]

New to open source. Would like to contribute, include me if possible

[rhuanjl]

Timings aren't looking good for the proposed meeting; with the current suggestions I'd have to hold 3 separate meetings in order to talk to everyone interested.

Is there a different day we should try OR could people have another look at options on the 12th? Aware we're coming from different time zones so it may be awkward...

[ppenzin]

@SumanthD welcome!

@rhuanjl looks like there is an overlap for everybody for the first slot on the schedule (the earliest available) - I can try attend, there are also similar times on 7th and 12th.

Oh, the joys of time zones - we might have to set up two meetings, three might be a bit much.

[rhuanjl]

@nli8n and @kmohan96214 please could you have a look at the time options for the 12th? WOuld like to see if we can make this meeting work next week.

@SumanthD and @Fly-Style please could you both also have a look at the doodle poll above and see if you'll be free any of the times on the 12th that others can do?

Would be good to arrange a meeting with most of us if possible.

[kmohan96214]

@nli8n and @kmohan96214 please could you have a look at the time options for the 12th? WOuld like to see if we can make this meeting work next week.

@SumanthD and @Fly-Style please could you both also have a look at the doodle poll above and see if you'll be free any of the times on the 12th that others can do?

Would be good to arrange a meeting with most of us if possible.

@rhuanjl updated

[rhuanjl]

Thanks everyone - we'll have the meeting this Saturday at 2pm GMT/UTC on Zoom

Link to join: https://us04web.zoom.us/j/76054667112?pwd=T2NOV25seCtLM1J2ZDdIY3dMNFNoZz09
Or login if you have zoom: ID: 760 5466 7112 Passcode: kt6Z9H

We'll aim to gather thoughts and draw up a forward plan for Chakracore, anyone's welcome though I'm hoping as a minimum everyone who has responded to the doodle will come.

[rhuanjl]

Here are a few rough ideas for things to discuss in the meeting in ~1 hour's time:

1. Background and how we've got to where we are.
2. How involved people would like to be in future CC work AND how much time we actually have.
3. Process for taking ownership of CC, moving beyond microsoft support. (including community run CI and release channels?)
4. How and when we should aim at our first community release - we had initially planned one for June but this did not happen.
5. How to balance:
   
   
   
   • documenting CC's current architecture/improving accessibility for contributors
   
   
   • refactoring/fixing tech-debt issues
   
   
   • increasing xplat support (arm-linux, arm-macos, x86-linux)?
   
   
   • new language features/standards compliance
   
   
   • performance work
   
   
   • API enhancements
   
   

Previous documents that may be helpful but are out of date:
https://github.com/chakra-core/org/blob/master/ChakraCore%20Future%20Plan.md
https://github.com/chakra-core/org/blob/master/Release%201.12%20plan.md

[ppenzin]

Follow on meeting (free Zoom meetings expire in 40 minutes): https://us04web.zoom.us/j/71287281690?pwd=Smo4c3F2ek5yaFpKVlB5Nmo4a0lyUT09

[rhuanjl]

Highlights following the meeting:

1. The repository is now going to be transferred into a community org.
2. @ppenzin is going to take the lead on setting up new community controlled CI
3. Other key areas of work will be tracked through github projects - please see the projects tab at the top of the page - all contributions welcome
4. We will have another meeting in early January and consider a release plan and what is feasible vs where we are
5. For instant communication with the community developers please join our discord channel: https://discord.gg/eDpj2auqcT

[rhuanjl]

Giving this a bump - we never organised the january meeting but some work has been happening. The repository is now under community control and we have our own CI running (special thanks to @ppenzin )

I propose we plan another meeting in ~2 weeks time to talk about the roadmap from here.

We are of course still (and always) looking for more volunteers. Anyone should feel welcome to have a look at any issue marked "Help Wanted" or "Good First Issue" and give it a go - please feel free to tag me in anything that needs explanation.

[ppenzin]

I'd be happy to have another chat. What does everybody else think?

[muhdmud]

Sounds good, count me in :)

[rhuanjl]

Contributor catch up (any newcomers welcome) should happen on our discord server via voice chat.

Based on previous availability I'm going to suggest 2pm UTC next saturday; if this isn't an option let me know.
Discord invite for anyone new is here: https://discord.gg/eDpj2auqcT

[ppenzin]

@Taritsyn do you want to join as well?

[Taritsyn]

@rhuanjl @ppenzin Thanks for invitation, but my spoken English is almost zero. Moreover, I do not write in C++ and currently only help to improve NuGet packages.

[ppenzin]

Sorry for taking this long to reply, did not check notifications for some time, need to clear the clutter.

@rhuanjl @ppenzin Thanks for invitation, but my spoken English is almost zero. Moreover, I do not write in C++ and currently only help to improve NuGet packages.

Having "fluent" level of spoken English is not a requirement, and NuGet contributions are actually very important. We will be glad to talk to you there, but it is entirely up to you.

@rhuanjl should we create separate issues for new meetings? Also, we can probably use the 'org' repository to host meeting-related content.

[Taritsyn]

@rhuanjl @ppenzin In principle, you can ask me any questions by e-mail.

Now the main thing is to decide whether we have the opportunity to install the Mono and cross-platform PowerShell.

[rhuanjl]

@rhuanjl should we create separate issues for new meetings? Also, we can probably use the 'org' repository to host meeting-related content.

I posted on this issue just because it's going to notify everyone who expressed interest before - agreed we should put more planning type stuff in the org repository going forward.