Experimental Osclass fork

[navjottomer]

Hi Guys,
I have recently created experimental fork of official osclass repo at https://github.com/navjottomer/Osclass
I started with refactoring old code and removing legacy code in Osclass and in future will try to add features, other's can also contribute to this repo by testing alpha release, creating issue or submitting pull request.
I will try to close as many issues I can in my free time, but I greatly need help of other developers who want to contribute in this repo.
Objective of this repo is to test new features and improving code quality in osclass, later we will create pull request to official Osclass repo.
Regards
Navjot tomer

[Aficionado]

Just be sure Osclass team AREN'T doing the same thing, in their offices, right now.

I mean don't do work/updating/refactoring that they are already doing (without updating Github).

[navjottomer]

Which I cannot be sure  without any official notification.
But it would be much better if people create pull request to this repo and after testing via community we create pull request to official one. We can add maintainer to this repo from community, who can decide what should be included and when. It will surely reduce work of official osclass repo maintainers.
We already know that official public repo is not touched in a while, if any core-dev can answer on this thread that how we can contribute more to this project.
I have already made over 65 commits to my repo so I will carry on what I am doing right now.
Regards

[Aficionado]

Just to be clear. I'm not saying "don't do it".

Au Contraire.

[navjottomer]

Ofcourse you didn't said that.

[Aficionado]

I'm not a programmer. I checked your github fork, and i was surprised to see the ammount of work you did.

I can't comment on the quality of it (i'm not qualified), but great thanks for your work and your interest in Osclass.

I wish this effort will be in benefit of Osclass and all of us.

 

[navjottomer]

Thanks!! Really appreciated. But you can always help by testing and reporting issue.
Regards

[Aficionado]

Thanks!! Really appreciated. But you can always help by testing and reporting issue.
Regards

And i will do so, if you let us know how ? I mean is it ready for test ? Where and how should we report something ?

Also did anyone from Osclass contacted you ? Anything from them ?

[navjottomer]

And i will do so, if you let us know how ? I mean is it ready for test ? Where and how should we report something ?
Also did anyone from Osclass contacted you ? Anything from them ?

You can check this page about how to create new issue https://help.github.com/articles/creating-an-issue/
You can get release from release section of GitHub page and test it in your local environment. Before reporting issue check if it is already fixed in later commit or not.
Keep in mind in starting stage we are more focused on errors not on feature. Because my first goal is to clean osclass code and than update few libraries osclass depends on.
Although I am not saying that you are limited to report errors only, you can create any issue just don't expect that it will be closed before our main goal( It may though).
From osclass team no one has contacted me yet but I have only posted about this yesterday So it is not their fault in anyway.

[marius-ciclistu]

Hi. Sorry to ask but  recentry I've read about drupal for example, and your description from here is verry similar with drupal's description, in the sense that it doesn't tell you concrete things, only a "nice story".
For example, it would be easier if you gave us some points of interest like: does your version strip the normal osclass of more features that it already doesn't have (excepting the plugins).

Take it as an observation with positive intention:).

Thank you.

[Aficionado]

Hi. Sorry to ask but  recentry I've read about drupal for example, and your description from here is verry similar with drupal's description, in the sense that it doesn't tell you concrete things, only a "nice story".
For example, it would be easier if you gave us some points of interest like: does your version strip the normal osclass of more features that it already doesn't have (excepting the plugins).

I don't see what "Drupal" has to do with this ReFactroring fork.

I think Navjottomer explained in details what his project is and what not.

[marius-ciclistu]

Only the description style. I for example did not understood what this fork is about by reading the above topic.
If I looked on github at some of the comits, I saw that he cleaned up the code for unnecesary brakets, parantesisis and other lines of code.

Osclass has many bugs that I resolved in my instalation, so if I would to use/test a new 'distribution' of osclass I would like to know the changes in functionality at least.

[Aficionado]

Only the description style. I for example did not understood what this fork is about by reading the above topic.
If I looked on github at some of the comits, I saw that he cleaned up the code for unnecesary brakets, parantesisis and other lines of code.

Osclass has many bugs that I resolved in my instalation, so if I would to use/test a new 'distribution' of osclass I would like to know the changes in functionality at least.

I think the following describes 100% the purpose of the fork.

I started with refactoring old code and removing legacy code in Osclass and in future will try to add features,

[marius-ciclistu]

refactoring old code and removing legacy code

These words made me write an answer
Refactoring old code - ok...I could imagine what that is.
Removing legacy code - I have no ideea what that does.

(I'm trying also to learn from this, so don't think my intentions are  negative).

[Aficionado]

refactoring old code and removing legacy code

These words made me write an answer
Refactoring old code - ok...I could imagine what that is.
Removing legacy code - I have no ideea what that does.

(I'm trying also to learn from this, so don't think my intentions are  negative).

I think if you look closely the Github fork you will understand fully what it is for.