...into the blue area of the application window, and you should get immediate feedback that either verifies the file or tells you what went wrong.
3 KB (381 words) - 19:03, 8 June 2007
...tp://creativecommons.org/contact#discuss email discussion lists] and share feedback and ideas in one of those forums.
146 KB (23,721 words) - 15:08, 9 October 2015
...ing|CC reconsidered this requirement]]. However, it was retained based on feedback from current and potential adopters that it is important for provenance, br
50 KB (7,125 words) - 18:33, 4 January 2016
...ms. There are undoubtedly bugs remaining and areas that need polish; your feedback will help track down those areas and provide suggestions.
3 KB (405 words) - 03:18, 20 March 2006
The Tracker works best when users and developers provide comments and feedback on specific issues. When writing comments there are some guidelines which
2 KB (349 words) - 20:56, 24 May 2016
....creativecommons.org/Podcasting_Legal_Guide.pdf available]. Please provide feedback at [[Talk:Podcasting_Legal_Guide]].</div>
....creativecommons.org/Podcasting_Legal_Guide.pdf available]. Please provide feedback at [[Talk:Podcasting_Legal_Guide]] (requires registration).</div>
112 KB (18,316 words) - 18:11, 27 February 2009
welcome your [http://creativecommons.org/discuss#metadata feedback]. (You can
5 KB (761 words) - 00:00, 7 July 2010
...tors, and developers. Creative Commons encourages others to provide ideas, feedback, comments and connections to other projects on this wiki page. There are m
4 KB (538 words) - 23:49, 14 July 2009
....creativecommons.org/Podcasting_Legal_Guide.pdf available]. Please provide feedback at [[Talk:Podcasting_Legal_Guide]] (requires registration).</div>
18 KB (2,626 words) - 02:08, 25 April 2006
....creativecommons.org/Podcasting_Legal_Guide.pdf available]. Please provide feedback at [[Talk:Podcasting_Legal_Guide]] (requires registration).</div>
5 KB (725 words) - 03:47, 11 May 2006
...ck] community to meet other developers interested in Creative Commons, get feedback on your projects, and talk with CC's full-time technology staff. You can al
We really appreciate community contributions and feedback (we're a small team and spread thin) and we especially love seeing what you
3 KB (362 words) - 15:24, 10 February 2023
....creativecommons.org/Podcasting_Legal_Guide.pdf available]. Please provide feedback at [[Talk:Podcasting_Legal_Guide]] (requires registration).</div>
...smedia.com/). The Guide is certainly a better product as a result of their feedback and comments. Finally, I am very thankful for Creative Commons' assistance
2 KB (369 words) - 17:36, 8 May 2006
....creativecommons.org/Podcasting_Legal_Guide.pdf available]. Please provide feedback at [[Talk:Podcasting_Legal_Guide]] (requires registration).</div>
2 KB (374 words) - 01:03, 27 April 2006
#redirect [[Salon 200605 Feedback]]
35 bytes (3 words) - 01:48, 15 September 2007
#redirect [[Salon 200605 Feedback]]
35 bytes (3 words) - 02:13, 27 April 2006
#redirect [[Salon 200604 Feedback]]
35 bytes (3 words) - 07:59, 27 April 2006
=== [[Toronto Salon 200605 Feedback|Feedback]] ===
3 KB (407 words) - 21:40, 20 December 2010
...e to upload items to the Internet Archive and would like to get additional feedback from users. Testers are encouraged to add bug reports and suggestions to [
918 bytes (133 words) - 16:44, 11 May 2006
...versions have received some testing, and are released here in order to get feedback and additional testing before releasing on addons.mozilla.org. Information
1 KB (175 words) - 20:37, 15 February 2007
Bugs, feature requests and feedback may be directed to the [[Mailing Lists|cc-devel]] mailing list or filed in
4 KB (613 words) - 01:00, 19 January 2016
Creative Commons does not provide support for this product. There is a feedback email on the [http://www.microsoft.com/downloads/en/details.aspx?FamilyID=e
2 KB (275 words) - 17:59, 20 April 2011
easy-to-use form and gather feedback. This is the welcome page to
11 KB (1,677 words) - 19:06, 9 August 2006
...is to put those guidelines up on the web in an easy-to-use form and gather feedback. This is the welcome page to that (as yet published!) questionnaire.
10 KB (1,676 words) - 00:33, 10 August 2006
=== [[Johannesburg Feedback|Feedback]] ===
3 KB (476 words) - 18:04, 24 June 2010
Perhaps the largest features in this release are to aid feedback
6 KB (836 words) - 16:33, 15 February 2012
== Feedback ==
1 KB (170 words) - 19:13, 21 December 2006
This page is for collecting feedback and brainstorming about next generation Creative Commons metadata.
212 bytes (24 words) - 21:22, 3 December 2006
This page is designed to collect comments and feedback on the *BETA* Returning Author's Rights: Termination of Transfer tool that
3 KB (464 words) - 00:14, 9 April 2014
Creative Commons regularly invites and receives feedback about its licenses and how they may be able to be improved to better serve
This feedback from both Debian and MIT was the impetus for CC commencing the version 3.0
36 KB (5,654 words) - 12:49, 17 November 2013
...ons [[Developers|Developer]] mailing list, and post your project ideas for feedback, before submitting your application
1 KB (229 words) - 03:26, 23 July 2009
== Feedback ==
...eatures you're interested in, or questions about the service, you can send feedback by:
3 KB (410 words) - 00:40, 9 May 2007
...better job at being more transparent and open to the community for ideas, feedback and participation?
7 KB (1,131 words) - 01:07, 5 February 2014
...ld wrap the flags to hide the bit-shifting -- but before I do that, I want feedback as to whether this design, in general, works.</del>
4 KB (567 words) - 21:58, 22 August 2007
===v1.0 testing feedback===
Please help CC make LiveContent the best it can be! Provide feedback under the following categories, or create your own!
9 KB (1,480 words) - 21:56, 5 May 2010
...s idea due to spamming/response issues? - think about other ways to gather feedback
3 KB (407 words) - 21:24, 18 September 2007
...w version, possibly [[version 3.5]] with more substantial changes based on feedback from [http://creativecommons.org/weblog/entry/7888 progress on license inte
8 KB (1,231 words) - 22:46, 10 September 2013
* Legal Project Lead produces a public discussion report detailing feedback: '''''two weeks'''''
3 KB (504 words) - 07:20, 26 May 2018
Please be patient and open to feedback -- we are all working together to write the most comprehensive and accurate
940 bytes (151 words) - 12:49, 12 November 2007
...talent build their profiles in a fun and encouraging environment, getting feedback by high-profile industry leaders (our '2bobmob') and building a focal point
1 KB (184 words) - 21:34, 29 October 2013
*implementing feedback into 3.0 (since Feb/Mar)
8) wait for feedback
40 KB (6,281 words) - 18:31, 21 November 2007
Please share your feedback on the talk page, either of this index or the pages of specific panels. Or,
7 KB (945 words) - 05:56, 28 October 2013
...uring 2008. You can track CC0's development, including an overview of the feedback we received and main revisions to the legal code, through our blog postings
16 KB (2,548 words) - 01:30, 2 March 2011
...tors, and developers. Creative Commons encourages others to provide ideas, feedback, comments and connections to other projects on this wiki page. There are m
4 KB (561 words) - 20:40, 13 February 2008
Details of each project are below. If you have any feedback, can help and/or contribute please contact Anna at creativecommons dot org
...siders an important friend. A first draft shall be completed for internal feedback in September 2012.
23 KB (3,589 words) - 08:31, 20 September 2013
...ed to confirm public domain status. Reliability is expected to improve and feedback by users is encouraged .
4 KB (570 words) - 09:20, 2 December 2013
...sions|new versions]] of each class of licenses when warranted by community feedback and suggestions for improvements. As of this writing most license classes h
11 KB (1,637 words) - 17:15, 17 April 2008
...the opportunity to generate exposure, make industry contacts, and receive feedback and critical appraisal from peers and industry experts, with an aim to impr
...igh-profile and successful industry professionals who provide constructive feedback and advice to 60Sox members. These professionals comment on six items from
6 KB (887 words) - 22:23, 3 September 2010
...Once the new track has been uploaded, the musician will be able to receive feedback via comments and ratings from other members. [http://ear-drum.org CCMCP’s
...ieve the creator should define the purpose for their work and based on our feedback we can say that people believe the purpose of creating is to share, at the
9 KB (1,467 words) - 21:19, 7 September 2010
...mons with attribution as our default position has been widely accepted and feedback has been that it has been instrumental in building Otago Polytechnic’s re
...consulted in the review, which occurred over the past two years, providing feedback that the institution needed to be more open to support creative thinking an
5 KB (711 words) - 04:25, 27 January 2014
...ology] and [http://www.uow.edu.au/ University of Wollongong], and received feedback from various digital media workers and artists acting as beta testers. The
6 KB (957 words) - 00:42, 27 March 2012
