Hello,

i am new to Project Euler and i really like the idea of this site.

As i am moving towards a new programming language (and started that as a profession) i wanted to keep track of my progress and share the code i created publically on my github (gists) page.

However, there is a section in the about page 'I learned so much solving problem XXX so is it okay to publish my solution elsewhere?' where it says that this may not be wanted.

Am i worrying to much about this or is that meant for blogging or other ways of sharing of solutions? (As i am quite new to all of this i am pretty sure i won't get to far anyway as i have no mathematic background either - i'll just find out )

Thanks!

Ery

## Publishing the Solution (About-Site)

### Re: Publishing the Solution (About-Site)

Yes,

it concerns all publishing outside Project Euler.

If you want to save your solutions you can do so locally on your computer, usb stick or external hard drive.

Alternatively you can make your github repo private.

Public repos, blogs etc are not allowed. The about page and the message you see when you have solved a problem are quite clear about that.

it concerns all publishing outside Project Euler.

If you want to save your solutions you can do so locally on your computer, usb stick or external hard drive.

Alternatively you can make your github repo private.

Public repos, blogs etc are not allowed. The about page and the message you see when you have solved a problem are quite clear about that.

### Re: Publishing the Solution (About-Site)

Thank you for your answer.

Thought that wouldn't fit to host my code on github for personal use (though publically visible) because i've already seen a few posts about Project Euler wich included code.

Now doing that with (secret) gists!

Thought that wouldn't fit to host my code on github for personal use (though publically visible) because i've already seen a few posts about Project Euler wich included code.

Now doing that with (secret) gists!

### Re: Publishing the Solution (About-Site)

Is it ok if I hide my documentation (one page per problem) behind a password that is equal to the solution? So, only solvers can see and discuss with me!

- euler
- Administrator
**Posts:**3634**Joined:**Sun Mar 05, 2006 4:49 pm**Location:**Cheshire, England-
**Contact:**

### Re: Publishing the Solution (About-Site)

@nida78: It means a lot to the team when members, like you, recognise how much we value the problems that we have created and what can be gained by first solving the problem for yourself. It is disappointing that a small number of people have chosen to deliberately and thoughtlessly spoil many of the problems by openly publishing solutions/answers. We think that your method of hiding the details of solutions behind a password equal to the answer is a very smart way of handling this situation. We wish you luck and thank you for the willingness you have shown to share your knowledge and passion for solving our problems. The only request we make is that you try to restrict yourself to the earlier problems.

*impudens simia et macrologus profundus fabulae*

### Re: Publishing the Solution (About-Site)

Hello,

First of all, I wanted to sincerely apologize, for until today I had public GitHub repositories showcasing some project euler solutions. I was using these repositories mainly as a means to showcase my coding skills to potential employers. What I have done now is made the repositories private but still accessible via a unique link through gitfront.io so that I can continue to share them with potential employers. Is this acceptable? I guess it is possible that a person looking at my resume would use my solutions on project euler themselves, but I feel like this is highly unlikely.

First of all, I wanted to sincerely apologize, for until today I had public GitHub repositories showcasing some project euler solutions. I was using these repositories mainly as a means to showcase my coding skills to potential employers. What I have done now is made the repositories private but still accessible via a unique link through gitfront.io so that I can continue to share them with potential employers. Is this acceptable? I guess it is possible that a person looking at my resume would use my solutions on project euler themselves, but I feel like this is highly unlikely.

- RobertStanforth
- Administrator
**Posts:**1690**Joined:**Mon Dec 30, 2013 11:25 pm

### Re: Publishing the Solution (About-Site)

Dear kromatic,kromatic wrote: ↑Thu Feb 25, 2021 12:32 am Hello,

First of all, I wanted to sincerely apologize, for until today I had public GitHub repositories showcasing some project euler solutions. I was using these repositories mainly as a means to showcase my coding skills to potential employers. What I have done now is made the repositories private but still accessible via a unique link through gitfront.io so that I can continue to share them with potential employers. Is this acceptable? I guess it is possible that a person looking at my resume would use my solutions on project euler themselves, but I feel like this is highly unlikely.

Thank you for being so considerate in keeping your Project Euler solutions private.

As it happens, we have a more relaxed approach with the first 100 problems. Whenever you solve a problem, the following note is displayed:

The rule about sharing solutions outside of Project Euler does not apply to the first 100 problems, as long as any discussion clearly aims to instruct methods, not just provide answers, and does not directly threaten to undermine the enjoyment of solving later problems. Problems 1 to 100 provide a wealth of helpful introductory teaching material and if you are able to respect our requirements, then we give permission for them to be discussed elsewhere.

### Re: Publishing the Solution (About-Site)

Here is an example of your publishing your solutions:

https://hoppi.neocities.org/ProjectEuler/solutions.html

You need to submit the answer to a problem to see my code in action.

https://hoppi.neocities.org/ProjectEuler/solutions.html

You need to submit the answer to a problem to see my code in action.