Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

What happened to codidact / core project in ASP.NET?

+6
−0

Several months ago when I first took a look upon Codidact project, I saw that it is using ASP.NET Core 3.1 and I said to myself that this is a project that I can contribute to. This frameworks seems to be the most loved web framework according to SO survey.

Unfortunately, things happened and I only revisited the project a couple of weeks ago and saw that the project is archived.

I tried to understand what happened and found this thread:

What we’re not going to do is stop any development on C# at all. We’ve got some talented developers working on our C# solution who may not be able to switch to Ruby, and it would be a waste to leave them with nothing to do. Practically, this decision is likely to run more like running both solutions in parallel - development on C# will keep going, just with the pressure taken off, giving the team the time to make sure it gets done right.

What happened to the Codidact/core project?

Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

1 answer

+9
−0

There was no progress on the C# project for months - it had gone entirely quiet, due to a lack of people available who were familiar enough with the language to contribute. While C# was chosen as the ideal language stack when the Codidact project started, it became apparent that it wasn't realistic currently for development to progress on it to bring it to MVP (minumum viable product).

Since instead QPixel - the Ruby version of the code that Codidact is currently running on - was seeing much more agile development and rapid progress, and C# was seeing little to none, it was decided to archive the C# project for now and focus on bringing QPixel to MVP, simply because that's a much more realistic goal with the current developer base involved in the project.

An announcement was posted in the channel #csharp-announcement on Discord by a project Admin on July 12th, 2020:

@Group Leaders and specially @Contributor/Backend, we've made this channel and pinged you to let you know that there's been no progress with our initially chosen tech stack of C# because of our lack of people actively working on it, Its been months now. We've decided that we complete MVP with qpixel and leave C# aside for now (archive it) to give it all the time it needs to come at the same level as qpixel (also for the future). Doesn't mean we'll be abandoning C#, we'll just defer it till the time its ready for action.

Why does this post require moderator attention?
You might want to add some details to your flag.

0 comment threads

Sign up to answer this question »

This community is part of the Codidact network. We have other communities too — take a look!

You can also join us in chat!

Want to advertise this community? Use our templates!

Like what we're doing? Support us! Donate