Actions
Forum Thread Details
  • Replies 7 replies
  • Subscribers 128 subscribers
  • Views 3175 views
  • Users 0 members are here
Related

A Good Reason to Read the element14 Community's Terms and Conditions

rscasny

All my programs include Terms & Conditions. It's a good idea to read them. I realize they are sort of boring, but they provide important information. 

During this past week, one of the Path to Programmable 3 participants decided to return the kit. He was reluctant to post his program blogs on the element14 Community. He wanted to post them on github and I guess link them to the element14 Community. 

Apparently, he did not read our terms and conditions or my notification letter regarding his selection as a finalist for the program.

We require that you must post all the deliverables (training blogs and final projects) to the element14 Community in the Path to Programmable 3 group.

Now, you are welcome to link your element14 Community blogs and projects to other websites. In fact, that would be great and much appreciated. But the original ones need to be published on the element14 Community.

The element14 Community has several functions. Being a content publisher is one of its more basic functions. We promote your content through social media, newsletters, and other kind of marketing campaigns. In fact, at times our content gets published in our industry's trade magazines. The sponsor also promotes our programs. Hence, your content must be published on the element14 Community.

While having quite a few email exchanges with this individual, I got the sense he was working on something proprietary (I guess you could call it) and he was concerned about "fidelity," which I guess means someone using his ideas, though I'm not quite sure. Well, all content published on the element14 Community is open to the public. If something is so private, then perhaps you should blog about something else. 

In any event, I encourage you to read the terms and conditions.

So, he is returning the kit to us. This is unfortunate because it could have gone to someone who was willing to abide by the rules we set forth in our T&Cs.

Randall

Path to Program 3 Program Manager

  • It would be nice to always highlight differences in T&C since previous contest. Sometimes only few words change and sometimes there are big differences. To be frank, I read terms and conditions only twice and in most other cases I assume they do not change.

    Almost all rules make sense. Few rules from terms and condtions are legal words which are hard to read (especialy for non-native english speakers) but at the end they also make sense. I am suprised that someone thought that Path to Programble is just a giveaway and private project sponsorships. At last, I think that for the particular member it would be cheaper to spend two weekends by creating some simple replacement open-hardware project and writing few blogs about it instead of paying for a return and loosing hardware which he/she used in his (most probably more valuable) private project.

  • in reply to misaz

    There are few changes to our terms and conditions. I think lately if there have been changes, it has been to clarify something. But as far as blog writing and deliverables, there should not have been any changes. It's always been the case that participants have to post their work on the element14 Community.

  • Writing up your content on E14 is hardly a minor point hidden away in the small print. It's the whole point of the challenges, contests and road tests!

  • With path to programmable III. I have to update my system and have to learn a lot of new things that were not part of the design challenge that took me more than 7 to 10 days to accomplish it. like knowing about boot partition table. Creating a bootable USB stick with various types of software etc and many more. It is some of the reason. we were not able to deliver project on time there are a little bit of delay in it. But I never asked to extented the competition for a month or so. But I do ask Rscancy to broaden the content requirement to ethical hacking and cracking as well. I believe it will be an interesting and useful topic for everyone to know about in general software security.

  • in reply to manojroy123
    manojroy123 said:
    broaden the content requirement to ethical hacking and cracking as well.

    Why would that have to be a requirement? You can always write about it, and make your posts stand out that way.

  • in reply to manojroy123

    It's great that you have learned new things. But this program is a training program, that is, one's first experiences with these products and technologies. Ethical hacking, etc. seems to be beyond the scope of this program. 

    Randall

    -the element14 Community team.

  • in reply to rscasny
    rscasny said:
    Ethical hacking, etc. seems to be beyond the scope of this program. 

    I personally wouldn't entirely overlook it though, if it comes up in hardening or 'blue-teaming' the protection of the setup as that's often overlooked in embedded hardware and setups. Voltage glitching is something that's a bit more specialised in protecting against though.