(shamelessly copied and then modified from junkdruggler's post here)
This is a DEVELOPMENT section, not GENERAL. Do NOT post questions here!
Before continuing, read this post: http://forum.xda-developers.com/showthread.php?t=729511. It also contains a link to XDA's rules, read those as well !
Let's try to post our ROMs and threads the following way to make the forum quicker and easier to access:
Code:
[KITCHEN][WWE][08.08.08] KOKOTAS ELF(in) Hybrid Kitchen (version 1.3)
[PRJ][WWE][BETA] BRAM / NOONSKI Touch Surface 6.1 Public Beta Release Candidate Unskinned
[REF] NOONSKI Cooking Class Class of 2008/09
[UPG] HTCTOUCHP New USPLs & IPLs for Elf & Elfin
[ROM][EUR][UPD][11-07-10] Doc's BareboneGalaxy v6 [2.1-u1~XWJG3][LauncherPro BETA] Optmized APKs [Barebone]
[ROM][ARA][UPD][11-07-10] ??? v1.1 [2.1-u1~XWJG3][TouchWiz 3.0] ??? [FullArabic]
[ROM][EUR][UPD][06-07-10] MoDaCo r2 [2.1-u1~XWJG1][TouchWiz] JG1/SwypeFix [OnlineKitchen]
For ROM releases, use:
Code:
[ROM][%region%][%variant%][dd-mm-yy] %name% %version% [%Androidbuild%~%baseROM%][%launcher%] %mchangelog% [%specialfeature%]
Variables as follows:
%region% - If this is an update.zip the region of base firmware. If you focus your ROM on a specific language/country put it here. Use abbreviations: EUR (Euro), ARA (Arabic), USA (United States)
%variant% - Not very useful right now since we can only use update.zip. Will become important once we get complete android builds. Use abbreviations: UPD (Update), FW (Firmware)
%name% - Name of your ROM. Whatever you want to call it.
%version% - The version of your ROM.
%Androidbuild% - This is the basebuild of android that the firmware uses. 2.1-update1 for the firmwares we have available right now. (Make it short: 2.1-u1)
%baseROM% - This is the last five symbols of the firmware you base your ROM on/that is required to install your update.zip. for example: XWJG3
%launcher% - This is the launcher you use (preferably with the version used).
%mchangelog% - Give one or two of the most important changes in this update.
%specialfeature% - One special feature of your ROM. Barebone or Online kitchen or something like that qualifies
Just some examples based on the available ROMs
[ROM][EUR][UPD][11-07-10] Doc's BareboneGalaxy v6 [2.1-u1~XWJG3][LauncherPro BETA] Optmized APKs [Barebone]
[ROM][ARA][UPD][11-07-10] ??? v1.1 [2.1-u1~XWJG3][TouchWiz 3.0] ??? [FullArabic]
[ROM][EUR][UPD][06-07-10] MoDaCo r2 [2.1-u1~XWJG1][TouchWiz] JG1/SwypeFix [OnlineKitchen]
For upgrade tools (HSPL, SSPL, CID, SIM, etc.), use:
Code:
[UPG] Description
For complete kitchens, use:
Code:
[KITCHEN][Language] name and version (Build)
For projects, use:
Code:
[PRJ] description
For utilities, use:
Code:
[UTIL] name and version
For reference threads (tutorials, guides, etc.), use:
Code:
[REF] description
A good start to a good structure
I have tried creating a standard for the ROM naming before but for lack of a sticky, there is so far only one "chef" who uses it.
http://forum.xda-developers.com/showthread.php?t=723745
Interesting. I've just copy/pasted a different post who'se layout reminds me of other sections I've moderator, and which will look familiar to users coming from the WM forums to here. I am of course open to suggestions!
Let's discuss, critisize, and formalize. Your way of naming looks smart to me, so let me share my comments.
Your original:
[%variant% ~ %region%] [dd/mm/yy] %Name% {%version%} [%Androidbuild% ~ %baseROM%] {%launcher%} %mchangelog% [%specialfeature%]
Variables as follows:
%variant% - Not very useful right now since we can only use update.zip. Will become important once we get complete android builds (Update or Firmware)
%region% - If this is an update.zip the region of base firmware. If you focus your ROM on a specific language/country put it here.
%Name% - Name of your ROM. Whatever you want to call it.
%version% - The version of your ROM.
%Androidbuild% - This is the basebuild of android that the firmware uses. 2.1-update1 for the firmwares we have available right now. (Make it short: 2.1-u1)
%baseROM% - This is the last five symbols of the firmware you base your ROM on/that is required to install your update.zip. for example: XWJG3
%launcher% - This is the launcher you use (preferably with the version used).
%mchangelog% - Give one or two of the most important changes in this update.
%specialfeature% - One special feature of your ROM. Barebone or Online kitchen or something like that qualifies
Just some examples based on the available ROMs
[Update ~ Europe] [11/07/10] Doc's BareboneGalaxy {v.6} [2.1-u1 ~ XWJG3] {LauncherPro BETA} Optimized APKs [Barebone]
[Update ~ Arabic] [11/07/10] ??? {v1.1} [2.1-u1 ~ XWJG3] {TouchWiz3.0} ??? [FullArabic]
(Sorry for the questionmarks. I don't speak/read arabic. I wish I could :/)
[Update ~ Europe] [06/07/10] MoDaCo {r2} [2.1-u1 ~ XWJG1] {TouchWiz} JG1/SwypeFix [OnlineKitchen]
Click to expand...
Click to collapse
I would keep the [ROM] prefix, just to distinguish it from normal programs, utilities, upgrades, tutorials, etc.
I would also use abbreviations to keep things short, and cut down on whitespace. variant = [UPD/FW], region = [EUR/ARA/USA/....], AndroidBuild / baseROM, without the spacing. To prevent overkill of brackets, I would not bracket the version. Also as we are using dd/mm/yy notation, AFAIK it is more common to use - instead of /. And I really just hate curly brackets, but that's personal
Example:
[ROM][EUR][UPD][11-07-10] Doc's BareboneGalaxy v6 [2.1-u1~XWJG3][LauncherPro BETA] Optmized APKs [Barebone]
Comments ? Suggestions ?
Chainfire said:
Interesting. I've just copy/pasted a different post who'se layout reminds me of other sections I've moderator, and which will look familiar to users coming from the WM forums to here. I am of course open to suggestions!
Let's discuss, critisize, and formalize. Your way of naming looks smart to me, so let me share my comments.
Your original:
I would keep the [ROM] prefix, just to distinguish it from normal programs, utilities, upgrades, tutorials, etc.
I would also use abbreviations to keep things short, and cut down on whitespace. variant = [UPD/FW], region = [EUR/ARA/USA/....], AndroidBuild / baseROM, without the spacing. To prevent overkill of brackets, I would not bracket the version. Also as we are using dd/mm/yy notation, AFAIK it is more common to use - instead of /. And I really just hate curly brackets, but that's personal
Example:
[ROM][EUR][UPD][11-07-10] Doc's BareboneGalaxy v6 [2.1-u1~XWJG3][LauncherPro BETA] Optmized APKs [Barebone]
Comments ? Suggestions ?
Click to expand...
Click to collapse
Those sound to me like sensible modifications. Now that I think back on it the curly brackets weren't really necessary ;-) And the date... my version of Windows displays the date as dd/mm/yyyy so I'm really at a loss what is convention here. but it really doesn't matter. I like the dashes too
Alright, updated first post with the changed information.
Structure is badly needed! all people are polluting this forum with topics with only questions!
Nice kang
I think most of what I said came from a stericson post... not sure though... I like READ MEs... and stickies... and FAQs...
I see only 2 ways you are EVER gonna be able to enforce this:
1) you go modo crazy and start deleting/moving stuff massively
tho you might get tired of doing so after a week or 2 ^^
2) you find somone that can modify the vbulletin post/reply form, so that it integrates the exact syntax you'd like ppl to use to post, and deny posts if it's not correctly filled out.
GL
This does not require enforcing, nor is it an exact science.
Conventions like there are used all over XDA and are generally followed. As soon as a number of the top releasers start following it in a subforum, the rest will eventually follow. It will take a while, sure... but it will happen, once the beginners realise that a structured life is a better life.
You have the option to do things nice and structured, or you can make a mess of things, but hey it'll be the mess you have to wade around in
Well said, I like the XDA naming scheme, seems to work well. Is there a mod for this section yet? someone to sticky important posts for now would do
There's an official mod, yes, and there's me. But I'll be off on vacation in a few days, for several weeks ...
Dear Friends.
I am using GoaTrip Rom on my SGS GT i9000. Now that this rom has loads of problems, I want to install Darky's ROM.
Cud somebody help with the procedure to do the needful.
Step by Step procedure will be helpful.
Plz reply to my PM - [email protected]
Regards
M Fahim
You need to study the step-by-step of whatever ROM you choose.
Related
Hi all you chefs out there.
As you all know the SGS is an awesome. Awesome devices have the tendency to get lots of chefs cooking even more ROMs.
In order to keep F/Ws and new releases managable it is handy to have a standard naming system for the threads in which the ROMs are released. This works best if we start sticking to one standard as early as possible because it's hard to adapt once you have 50+ ROMs threads. So here is my proposal:
[%variant% ~ %region%] [dd/mm/yy] %Name% {%version%} [%Androidbuild% ~ %baseROM%] {%launcher%} %mchangelog% [%specialfeature%]
Variables as follows:
%variant% - Not very useful right now since we can only use update.zip. Will become important once we get complete android builds (Update or Firmware)
%region% - If this is an update.zip the region of base firmware. If you focus your ROM on a specific language/country put it here.
%Name% - Name of your ROM. Whatever you want to call it.
%version% - The version of your ROM.
%Androidbuild% - This is the basebuild of android that the firmware uses. 2.1-update1 for the firmwares we have available right now. (Make it short: 2.1-u1)
%baseROM% - This is the last five symbols of the firmware you base your ROM on/that is required to install your update.zip. for example: XWJG3
%launcher% - This is the launcher you use (preferably with the version used).
%mchangelog% - Give one or two of the most important changes in this update.
%specialfeature% - One special feature of your ROM. Barebone or Online kitchen or something like that qualifies
Just some examples based on the available ROMs
[Update ~ Europe] [11/07/10] Doc's BareboneGalaxy {v.6} [2.1-u1 ~ XWJG3] {LauncherPro BETA} Optimized APKs [Barebone]
[Update ~ Arabic] [11/07/10] ??? {v1.1} [2.1-u1 ~ XWJG3] {TouchWiz3.0} ??? [FullArabic]
(Sorry for the questionmarks. I don't speak/read arabic. I wish I could :/)
[Update ~ Europe] [06/07/10] MoDaCo {r2} [2.1-u1 ~ XWJG1] {TouchWiz} JG1/SwypeFix [OnlineKitchen]
It's just a suggestion for the chefs obviously but it would be great if you guys could do this for us. Makes choosing a suitable ROM a lot easier.
PS: Anything I missed/you would like to see in the 'standard'? Don't hesitate to post
Very good idea, coming from the Nexus One dev thread - they too seemed to have adopted this method of displaying their ROMs, Themes, etc and it makes everything much easier to find and navigate. So i really do hope everyone follows this standard.
Exactly my idea. Coming for the HTC Topaz section, I know what it's like to have everybody just used their own design to get attention. It's annoying and makes searching unnecessarily difficult.
@Chefs: PLZZZ use this ;-)
I agree completely.
Gooofy said:
I agree completely.
Click to expand...
Click to collapse
yes, support! this will make life easier for everyone
Small bump ;-)
Darkstriker said:
Small bump ;-)
Click to expand...
Click to collapse
Good idea with creating a standard for thread titles.
Thus I'll use it
We really need a mod. *bump*
^^^ I second that !
Needs another bump again :S
*minibump*
One way or the other, this is going into the [READ ME] sticky, so this thread is closed.
Below is a format that should be used as an example of how a rom thread should look. It doesnt have to be exact. I suggest that you stay creative and use all the features in the advanced panel when creating a thread.
1. Name of rom, team, etc
2. Introduction
3. Changelog in code or php tags
4. What's included in the rom in the (apps, tweaks, scripts, addons, mods) in code of php tags
5. What works/what doesn't work in code or php tags
6. Credits (Users name-with link to (profile/github/or thread u got tweak from embedded), and what they did to help you)
7. Screenshots (2-10 different screenshots of different aspects of rom)
8. Kernel with either link to thread you got it from or github (if stock sense or cm please state that and that is enough)
9. Instructions on how to install the rom (also if special instruction for a2sd or beats audio...etc)
10. Do's and Don'ts of the rom
11. Questions & Answers section (I find this helpful to write out asked questions with solutions at the bottom of the op. I find that it cuts down on the question being asked a million times)
12. Finally the dl link
13. Additional add-ons (this can go into first post or reserved posts after)
I find the embedded link looks and feels better throughout the op if possible.
All sections should have a header with enlarged text and spaced out so people can read it easily.
I am hoping that this helps to make this section a little cleaner and easier. enjoy
The way I look at this is that it takes US weeks/days/hours to make these roms....we can take the time out to make sure that the op looks professional and clean
Also Make sure the op is fully ready before posting. I know we all get excited to release a rom but stating that half the stuff will be updated as time permits just shows that you are lazy and in a hurry which doesnt look good cause if thats the case then how does your rom run....
No posting a a rom thread without a DL link either
Below is a format that is a guideline to be used as an example of how a rom thread should look. It doesn't have to be exact. I suggest that you stay creative and use all the features in the advanced panel when creating a thread.
Name of rom, team, etc
Introduction
Changelog in code or list tags
What's included in the rom in the (apps, tweaks, scripts, addons, mods) in code or list tags
What works/what doesn't work in code or php tags
Credits (Users name-with link to (profile/github/or thread u got tweak from embedded), and what they did to help you)
Screenshots (2-10 different screenshots of different aspects of rom)
Kernel with either link to thread you got it from or github (if stock sense or cm please state that and that is enough)
Instructions on how to install the rom (also if special instruction for a2sd or beats audio...etc)
Do's and Don'ts of the rom
Questions & Answers section (I find this helpful to write out asked questions with solutions at the bottom of the op. I find that it cuts down on the question being asked a million times)
Finally the dl link
Additional add-ons (this can go into first post or reserved posts after)
I find the embedded link looks and feels better throughout the op if possible.
All sections should have a header with enlarged text and spaced out so people can read it easily.
I am hoping that this helps to make this section a little cleaner and easier. enjoy
The way I look at this is that it takes you weeks/days/hours to make these roms....we can take the time out to make sure that the op looks professional and clean
Not to toot my own horn but here is a link to one of my own rom threads as an example. Link
Also Make sure the op is fully ready before posting. I know we all get excited to release a rom but stating that half the stuff will be updated as time permits just shows that you are lazy and in a hurry which doesn't look good cause if thats the case then how does your rom run....
No posting a a rom thread without a DL link either. If posted then the thread will be removed
Below is a format that is a guideline to be used as an example of how a rom thread should look. It doesn't have to be exact. I suggest that you stay creative and use all the features in the advanced panel when creating a thread.
Name of rom, team, etc
Introduction
Changelog in code or list tags
What's included in the rom in the (apps, tweaks, scripts, addons, mods) in code or list tags
What works/what doesn't work in code or php tags
Credits (Users name-with link to (profile/github/or thread u got tweak from embedded), and what they did to help you)
Screenshots (2-10 different screenshots of different aspects of rom)
Kernel with either link to thread you got it from or github (if stock sense or cm please state that and that is enough)
Instructions on how to install the rom (also if special instruction for a2sd or beats audio...etc)
Do's and Don'ts of the rom
Questions & Answers section (I find this helpful to write out asked questions with solutions at the bottom of the op. I find that it cuts down on the question being asked a million times)
Finally the dl link
Additional add-ons (this can go into first post or reserved posts after)
I find the embedded link looks and feels better throughout the op if possible.
All sections should have a header with enlarged text and spaced out so people can read it easily.
I am hoping that this helps to make this section a little cleaner and easier. enjoy
The way I look at this is that it takes you weeks/days/hours to make these roms....we can take the time out to make sure that the op looks professional and clean
Not to toot my own horn but here is a link to one of my own rom threads as an example. Link
Also Make sure the op is fully ready before posting. I know we all get excited to release a rom but stating that half the stuff will be updated as time permits just shows that you are lazy and in a hurry which doesn't look good cause if thats the case then how does your rom run....
No posting a a rom thread without a DL link either. If posted then the thread will be removed
OK, I will try to keep it short:
1) I don't have enough posts for answering Dynamics ROM thread. Therefore I am posting here.
2) I had been looking for Dynamics ROMs, but I could have not find any links. I decided to write PM to ultrashot and he replied I should have got Dynamics ROM kitchen and had built them myself. So I did.
3) I noticed a few people are looking for Dynamics ROMs as well. So I decided to start this thread.
4) Considering I have access to the kitchen, I can build (and upload) any Dynamics 2.4 build 21690 ROM variations : WM6.5/WM6.5.X, no Sense/Sense 2.1/Sense 2.5, WWE/GER/RUS. Just post your request & and be patient (I have a terrible upload).
5) The cooked ROMs are built following ultrashot's notes, so they should be identical. But as usual, I do not take responsibility for any damaged goods. Also, all credit goes to ultrashot. You should really thank this guy, he did one hell of a job.
6) The download links follows. The naming convention is same as ultrashot's (check the original Dynamics topic). Side note: chosen filehosting is popular Czech fileserver, pretty much what is uploaded there, it stays there forever. If you have any trouble downloading, post a reply.
ulozto.net/xJaGgrKw/dynamics-gtx-2-4-5-wwe-kovsky-7z
ulozto.net/x4N5q6Yt/dynamics-gtx-2-4-0-wwe-kovsky-7z