Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

Read Me Top 5 things to help you get started.

Malcolm

Administrator
Administrator
Staff Team
Code Plus
Company Plus
Top 5 things to help you get started
As a member of a growing community, it may seem almost next to impossible for you to get on board. However, it is not. It just requires a little bit of putting yourself out there.

Introduce yourself
If you are just a developer, site owner or even wishing to participate in the community. Then posting an introduction of yourself would be an excellent idea. You can briefly tell everyone who you are and what you are all about, this will allow members to get to know you which may benefit your project if you are interested in promoting one. When I take a look at other websites and browse through the sites listed, and I see someone posting a post inviting other members in joining his or her site but hasn't posted an introduction, I'll more than likely skip over it. By not posting an introduction; it's showing me that you don't want to get involved with the community. Which then makes me assume that you have that same type of attitude toward your project. So post an introduction and create a great first impression!
Click here to get started!

Add an Avatar
Although the default avatars can be lovely - We do like seeing new fresh faces and having your avatar would be shavy too! My favourite part of working in a community such as CodeForum.ORG is looking at all the new avatars everyone has. So add one... like right now...You can change or add your avatar by clicking your username in the top right corner, selecting profile > Profile Picture icon. From there you can upload an image, sync with Facebook or import from URL.


Edit your profile
Having a completed profile can help you in numerous ways, it can help you find potential projects to get involved with, help motivate other members in joining your project, and can help you make new friends! More friends = more love. You can edit your profile by clicking your username in the top right corner, selecting profile > Edit Profile.

Add your signature
Adding a signature can be an excellent way of promoting yourself & your project. You can edit your signature by clicking your username in the top right corner then select Account Settings > Signature.
You can also use this link.



Just say hey!
Start a conversation with someone! Go to their profile and say "Hey"!
Start with me!
Read the site-guidelines & rules!

It's essential that you know the rules, so you don't run into any trouble with the po-po. >
View the site-guidelines here.
 
Last edited:
Figured that I'd also add some of my tips to help you get started.

Get Involved With Q&As
When I say 'Q&A', I'm not talking about those ones that you'd find on a place like Reddit. I'm talking something above the ranks of StackOverflow. There are plenty of people here on CF who may not have a good amount of experience in a Language unlike you and may need assistance with something. Go and help them out if you think you can help them.

Suggest Stuff To Help Improve CF
So, apparently @Malcolm is always open to Suggestions to help improve CF. You can Suggest anything to him. It can be a particular issue with the Site, adding new things(Boards, Features etc.) or it can be to maybe remove something that is unnecessary. Whatever it may be, go and Suggest it. You can Suggest things in the Community Hub.

Again, these were just some additional tips to add onto @Malcolm's original post. As stated in his Post as well, make sure that you read the Guidelines, stay safe and just have fun with the rest of us here on CF.
 
Users can also submit projects for the CF Community to do.
They can post in the web, mobile app, and gaming development sections.
 
Weboogle said:
Users can also submit projects for the CF Community to do.
I'd like to add a couple things onto this.

First of all, know what your Project is, what it does, what it's core Features are and how it will be developed. This is important. If you're Project is an AI-Project then it must be able to communicate with the User. If it's a File-Uploading Service then the User must be able to upload. For core Features, again, if it's a File-Uploading Service then the core Feature will be the ability to upload and share Files. As for "How it will be developed," then you must have planned and know how it's going to be developed. Will it be hosted on GitHub, GitLab or GNU Savannah? Will it be written in Java, C++ or Perl? How will Contributors layout their Code? How will Code be reviewed? Ask yourself these types of questions. It will help you get an idea of how the Project will and should run.

Second of all, PM the Project to @Malcolm(Or some other Administrator). From then on, the Project that you've submitted will be reviewed and you may also be asked some questions while it's being reviewed. After it's reviewed, it will more than likely have passed, but if not, take the feedback that you've been given as to why it was rejected and then submit it again once you've applied that feedback. One thing to note though: There is currently no review-process for Projects. @Malcolm has yet to establish one(As of posting this, anyway). But, I plan on speaking to him about this.

Third of all, deciding whether you're Project should be put under your Username, under CF(CodeForum.org) or given to somebody else. What I mean by this is, say that you're currently working on your own Project. You don't plan to give it away to anyone. In that case, it's under your Name/Username. But, if you decide that you're not up for being the Maintainer of a Project and you decide to give it away to CF or someone else then it will either be under CF's GitHub or that other person's Name/Username. Choose carefully on deciding whether it will be under your Name, CF's or someone else's. Because once you give it away, it may almost be impossible to get it back under yours. But, I do assume that @Malcolm is happy to give a Project back to you if it's not working out under CF. You can also request for CF to scrap your Project entirely. But if it was given away to someone else then they may not delete or give you back your Project. So again, be careful when it comes to this.

Last but not least, is working on the Project under CF. If you decided to put your Project under CF and it passed then first of all, congratulations. Second of all, you still have complete control over the Project and nearly all of it's Repository(What I mean by nearly, is that when @Malcolm sets-up the Project under CF's GitHub, you do not have access to the Settings page of that Repository. That was the case with me and one of my Projects that was once under CF. I couldn't access the Settings for it. So, just remember that). Seeing as you have complete control over the Project and nearly the whole Repository, it means that you need to set-up the Directories(Source-Folders), apply a Text-File that explains the Project, apply a License to it and provide Documentation via .txt/.md Files or a Wiki for Developers who are contributing to the Project. You'll also need to be the one who kickstarts the Project. So that means writing those first lines of code all by yourself or with the help of a Co-Maintainer(If there is one). Also, I'd recommend maybe giving Status-Updates to @Malcolm or the Administrator who reviewed your Project from time to time(Around every 4 - 10 Months). This will let the Administrator know whether Development is going well or not.

I hope that gives you an idea of what to do when submitting a Project to CF. While having the idea of the Project and writing it on paper may make it seem easy, running the Project itself won't. You'll have a lot of setting-up to do. You'll also need to find a way to get more people on board with Development, Design, Reviewing and Testing. Also, remember that this is Free-Software('Free' as in 'Freedom'. 'Open-Source' if you find the other term more confusing than this one). So, anyone can take your Project and build a new one out of it, use it in the Development of their own Projects or submit and review Code in your Project. You cannot stop people from doing the things that I've listed above and trying to stop them from doing so, destroys the principles and values of Free-Software/Open-Source.

Good luck with your Projects everyone.
 
I'd like to add a couple things onto this.

First of all, know what your Project is, what it does, what it's core Features are and how it will be developed. This is important. If you're Project is an AI-Project then it must be able to communicate with the User. If it's a File-Uploading Service then the User must be able to upload. For core Features, again, if it's a File-Uploading Service then the core Feature will be the ability to upload and share Files. As for "How it will be developed," then you must have planned and know how it's going to be developed. Will it be hosted on GitHub, GitLab or GNU Savannah? Will it be written in Java, C++ or Perl? How will Contributors layout their Code? How will Code be reviewed? Ask yourself these types of questions. It will help you get an idea of how the Project will and should run.

Second of all, PM the Project to @Malcolm(Or some other Administrator). From then on, the Project that you've submitted will be reviewed and you may also be asked some questions while it's being reviewed. After it's reviewed, it will more than likely have passed, but if not, take the feedback that you've been given as to why it was rejected and then submit it again once you've applied that feedback. One thing to note though: There is currently no review-process for Projects. @Malcolm has yet to establish one(As of posting this, anyway). But, I plan on speaking to him about this.

Third of all, deciding whether you're Project should be put under your Username, under CF(CodeForum.org) or given to somebody else. What I mean by this is, say that you're currently working on your own Project. You don't plan to give it away to anyone. In that case, it's under your Name/Username. But, if you decide that you're not up for being the Maintainer of a Project and you decide to give it away to CF or someone else then it will either be under CF's GitHub or that other person's Name/Username. Choose carefully on deciding whether it will be under your Name, CF's or someone else's. Because once you give it away, it may almost be impossible to get it back under yours. But, I do assume that @Malcolm is happy to give a Project back to you if it's not working out under CF. You can also request for CF to scrap your Project entirely. But if it was given away to someone else then they may not delete or give you back your Project. So again, be careful when it comes to this.

Last but not least, is working on the Project under CF. If you decided to put your Project under CF and it passed then first of all, congratulations. Second of all, you still have complete control over the Project and nearly all of it's Repository(What I mean by nearly, is that when @Malcolm sets-up the Project under CF's GitHub, you do not have access to the Settings page of that Repository. That was the case with me and one of my Projects that was once under CF. I couldn't access the Settings for it. So, just remember that). Seeing as you have complete control over the Project and nearly the whole Repository, it means that you need to set-up the Directories(Source-Folders), apply a Text-File that explains the Project, apply a License to it and provide Documentation via .txt/.md Files or a Wiki for Developers who are contributing to the Project. You'll also need to be the one who kickstarts the Project. So that means writing those first lines of code all by yourself or with the help of a Co-Maintainer(If there is one). Also, I'd recommend maybe giving Status-Updates to @Malcolm or the Administrator who reviewed your Project from time to time(Around every 4 - 10 Months). This will let the Administrator know whether Development is going well or not.

I hope that gives you an idea of what to do when submitting a Project to CF. While having the idea of the Project and writing it on paper may make it seem easy, running the Project itself won't. You'll have a lot of setting-up to do. You'll also need to find a way to get more people on board with Development, Design, Reviewing and Testing. Also, remember that this is Free-Software('Free' as in 'Freedom'. 'Open-Source' if you find the other term more confusing than this one). So, anyone can take your Project and build a new one out of it, use it in the Development of their own Projects or submit and review Code in your Project. You cannot stop people from doing the things that I've listed above and trying to stop them from doing so, destroys the principles and values of Free-Software/Open-Source.

Good luck with your Projects everyone.
Thanks for your input, I responded to your message. :)

We will work on a review process, and release it to the community shortly.
 

New Threads

Latest posts

Buy us a coffee!

Back
Top Bottom