A while ago it happened that i saw a journal skin that looked very familiar to one of mine. After checking the code i realized that it was my journal skin and only images have been replaced.
Because of that and after writing a journal to remind people that it isn't right to do something like that, i was asked when someone can call a journal code their own.

First i wanted to give an explanation via reply, but after thinking about it i realized that this can't be answered easily and should be available for more than one person to read (and to be found later again easily as well).
That's why i asked my watchers and maybe random guests who visit me to tell me when they would consider a journal as their own or when someone could claim such as own code.

To avoid that the answer to that question will reflect just my opinion i will highlight a few opinions from the feedback i got after stating my own point of view on this matter as well.


For those of you who already used a install skin to create something new without the permission of the original creator: read this Free Journal Skins – What does that mean? carefully!

---

How do you code your skins?

Before we are even able to think about if you can call a certain journal code your own, we will need to differ between the ways of the creation.


Writing it all from scratch
If you are writing down the code on your own without looking at the code of other people or using resources(like tutorials, code snippets etc), then the code is yours. It doesn't even matter if you learned from tutorials years/months ago... if the code comes right from your brain it's your work. Still there is a "but" to keep in mind.

All the single bits of CSS code can't be protected. It's like protecting a single word(except brand names). It won't work.
However it is the combination of your code, with the colors and the images used, that makes it unique and yours. The more complex your code gets, the more unique it will become and it is yours.

Sounds simple, doesn't it?
In case you only use a very basic template, adding a background color, changing the font color and use a nice image at the top you own the layout/design, but claiming that code as your own and reporting other skins with the same style you won't be lucky, because it is not unique/special enough.




Using resources like tutorials and code snippets or references
You just started to write down the code for your new skin, but suddenly realize that you are stuck and can't get further. The next step would be either to ask a friend or to look for resources to help you out.

Here it all depends on the resources or friend of yours. Some ask for credit, some leave it up to you to add a little link as a thank you and some don't care about it at all.
Resources are made to help others out, means code snippets and tutorials have been created to give you the hint you need to go on. Sometimes it's just the explaining of common mistakes that makes you get further, sometimes you grab a code line from a tutorial and sometimes you need to heavily reference code from such resources(this does not mean to grab complete code parts from existing skins).

Whatever helps you to finish that skin, the result will be yours and you are able to redistribute it. The only exception comes to resources that clearly state that they shouldn't be used as is or for new skins without permission.
Adding a link to the resources in the description of the finished deviation won't hurt though, because it might helps others who are stuck as well.





Adjusting existing skins a bit
You are free to modify any skin you installed as long as you just use it for yourself, without redistributing it as a new skin. You agreed to certain terms of usage (see news link at the top of this article) before you installed the journal and can't redistribute it without the permission of the original creator.

If you have modified such a skin by replacing a few images and some colors the code won't have enough significant changes to be called your own. The main code of the skin you have used still remains, so it's not your code and you shouldn't redistribute it.
You could still ask the original creator if it is ok for them if you do so. And always ask before you upload anything, not afterwards or after they found that new skin on their own. Just a link back to the original skin won't work as permission either, because of said terms of usage you agreed to before.

So as long as someone could easily recognize the original skin just by looking at your "new work" you did not enough effort to have created something new/unique.




Adjusting existing skins a lot

Attention: This reflects my personal opinion and is no guarantee that you can modify any skin without getting into trouble!

Another thing is to grab an existing journal and modify it that much that you can't recognize the original anymore. That doesn't mean that you change the order of the code and use new images and other colors. It means that you use a skin as a reference, give it your style and really create something on your own in a way that you can't recognize the other skin by placing the code or design next to each other.
That is something you could claim as your own as well, however you should be fair and credit the original skin, as it was the starting point for you. Especially if you wouldn't be able to code it from scratch otherwise.




  Conclusion
The best way is to write down code from scratch and to make use of resources - there are plenty of them at #eCSSited. For everything else ask the creators of certain journal skins for permission or help to be safe.

---

Your Feedback

_{By =GillianIvy}
"I would have to say that it is the point that you are not using snippets from other people's works, able to type everything top to bottom on your own without looking at anything. Sure, referencing a definition which you forgot how to type properly but know how to do it is fine. But if it's a whole snippet of someone else's work, copied line by line... Then credit is a must."



_{By *Cinnamon-Heart}
"I believe it's more about the whole thing - how it looks, where are all the stuff positioned what kind of background style is used and how is everything put together. This is what makes the final skin after all. And if I start to code something from scratch right now and I want to place an image in the left bottom corner - I'll find a reference and I'll copy the code there. Most likely this is going to be the best code to put an image there so I won't change it. The second time I'll use my previous work as a reference. And by the next time I'll have it already memorized and I won't use a reference. Would that be different, should a credit someone in my first work but stop doing it at the third?"



_{By `electricjonny}
"Skins and CSS are mostly just copies of one another. And you're limited to a lot of constrictions dA puts in place for journals. So most skins are pretty similar. I guess, when you get right down to it, there is no original journal skins here. They're all referenced or copied from somewhere.[..]

Although this is an interesting concept, and there might be other things to consider. That's just my first initial response. Honestly, I get a bit fed up with shit tons of credits, either on skins or on the actual journal it's self."



_{By `thespook}
"I think it's a simple and clear line.

At first people will understand the basics of CSS, but maybe some complicated stuff is beyond their current learning. For them, they borrow code written by others that takes care of the magic for them. Here, the respectful thing to do is give credit where it's due.

Eventually though, they will come to understand CSS deeper. They will understand the magic behind the complicated stuff. At this point, they can write it from their head. At this point, they're not using someone else's pre-written code, so they have no one to credit but themselves."



_{By `PurpelBlur}
"I've never coded a skin of my own but, in my opinion, "the point" comes when you can code completely on your own, zero reference."



_By~Genisay
"Code is tricky because the over all product can be copyrighted, but individual parts of a products code are by their very nature open source. Like if a person made a....journal skin...then the skin as a whole belongs to them. If they drew the banner at the top, the image belongs to them...but the code that arranges it all could be disputed, or the code that sets the border placement or base colors."



_{By =Amarie-Veneanar}
"I think, these code parts are to be regarded as resource like a brush you've used to design a skin, because a deviant has put time into creating a specific part of code for a unique feature like the mini thumb feature. So, if they offer this code part for other dA members to use as a resource, of course they deserve to be credited each time you include their code part in your journal code."

---

Hope this will help to make things a bit clearer, but always keep in mind that it is mostly up to personal opinions (excepts the terms of usage when installing skins).
If you are still unsure and aren't sure if you can upload a skin you have created, feel free to either leave a comment here, on my profile or note me.

When talking of resources i only mean those who are related to code. If you use brushes, stock images or anything else like that follow the given rules of those deviations!




How to upload a journal template
Permission to use CSS skins needed?
Journal/Gallery templates – A Guideline
Free Journal Skins - What does that mean?





_{If you find any grammar or spelling mistakes you can keep them, there will be more in the future. Also this wasn't checked by other persons, so sorry if there are any general mistakes.
And sorry for so much text lol <3}